API versions
Semrush APIs are currently available in two versions. As the Semrush API platform evolves, new functionality will be introduced in a newer API version while existing integrations continue using earlier versions. To support both use cases, the documentation is organized by API version.
In this article, you’ll learn how API versions are organized, how API keys are associated with different versions, and how to find the correct documentation for your integration.
Jump to Available versionsAvailable versions
Semrush APIs are currently available in the following versions:
- Version 3 (
v3) - Version 4 (
v4)
Each version has its own API reference, authorization methods and requirements, and supported functionality.
Jump to Documentation portal structureDocumentation portal structure
The Semrush API portal is divided into version-specific sections.
Use the version selector in the upper-left corner of the portal to switch between available versions.
When you select a version, the documentation displays:
- API endpoints available in that version
- Authorization methods and requirements
- Supported API keys
- Version-specific guides and reference materials
Jump to API keys and authorizationAPI keys and authorization
Different API versions support different API keys and authorization methods. API keys determine which APIs you can access, while authorization methods determine how those keys or tokens are passed in API requests.
Refer to the documentation for your API version to ensure that you use the correct combination of API key and authorization method.
Jump to API keysAPI keys
API keys are version-specific. An API key created for one version cannot be used with another version.
You can find your API keys in the API keys section of your Semrush profile.
The v3 API key is used with Version 3 APIs. Each account has a single v3 API key that’s generated automatically and can’t be revoked or deleted.
The v4 API key is used with Version 4 APIs that support API key authorization.
Your account includes one autogenerated v4 API key that supports your existing integrations.
To set up a new integration, you need to create a new v4 API key.
You can create up to 100 v4 API keys, each with its own permissions and expiration settings (TTL). v4 API keys can be renamed, revoked, or deleted.
v3 API keyv3Jump to AuthorizationAuthorization
Each API version has its own authorization requirements, supported API keys, and authorization methods.
For information about obtaining, managing, and using API keys, as well as supported authorization methods and implementation examples, refer to the authorization article in the corresponding documentation version:
Last updated: July 15, 2026