Semrush API v4 migration overview

If you have an integration built on v3, migrate it to v4 before the shutdown date.

• SEO API migration guide
• Semrush API v3 and v4 comparison reference

Jump to Key datesKey dates

We’ll publish the exact shutdown date on this page at least 3 months in advance and notify affected accounts by email.

Jump to What changes in v4What changes in v4

• Clearer requests. Endpoint URLs identify operations, replacing the type parameter used by most v3 reports.
• Clearer responses for AI agents. Descriptive field names and enum values help agents interpret results. Response metadata shows the parameter values used.
• Control access per integration. Create up to 100 keys, each with its own permissions and expiration date.
• Control team usage. Set monthly API Unit limits for your corporate subusers and track individual consumption.
• JSON for easier integration. Use JSON in applications and automated workflows, with CSV available on supported endpoints.
• More secure authentication. Send API keys in the Authorization header to keep them out of URLs.

Jump to How to migrateHow to migrate

1. Get a v4 API key.
2. Find each v3 endpoint that your integration calls in the Method mapping and note its v4 equivalent.
3. Check Request parameter differences and Response parameter differences. Some request parameter names and response shapes have changed.
4. Update and test your integration against v4.
5. Switch your integration endpoint by endpoint.

Full SEO API migration guide ›

Jump to If there’s no v4 equivalentIf there’s no v4 equivalent

The method mapping uses these statuses:

• Coming soon in v4: A v4 equivalent is planned. Keep using v3 for now. The Method mapping is updated when it ships.
• Not covered by v4: No v4 equivalent is planned. Contact Support to discuss alternatives.