Keyword.com Google SERP Tracker API v2
Introduction
The Keyword.com API empowers developers to programmatically access and manage keyword ranking data, giving you the same core functionality available in the Keyword.com interface. Whether you’re building an SEO tool, a content marketing platform, or a performance dashboard, our API delivers the data and insights needed to grow search visibility and drive traffic.
This documentation covers everything you need to get started:
-
Authentication using secure headers
-
RESTful endpoints for managing projects and keywords
-
Practical examples of requests and responses
-
Tips for efficient, scalable integration
Getting Started
To use the API, you’ll need an API token. If you don’t have one yet, create an account on Keyword.com and retrieve your token under Settings > Account tab.
Once authenticated, you can:
-
Retrieve project and keyword ranking data
-
Add and delete keywords
-
Trigger on-demand keyword refreshes
-
Access custom shareable view links for reporting
-
And more...
With this API, you can integrate Keyword.com into your internal tools, automate SEO workflows, and scale your keyword tracking operations.
Authentication
The Keyword.com API uses token-based authentication via HTTP headers for secure access.
Required Header
Include the following header in all your API requests:
Authorization: Bearer [API_TOKEN]
Example:
curl --location 'https://app.keyword.com/api/v2/groups/Apple/keywords/272678916' \
--header 'Authorization: Bearer [API_TOKEN]'
API Token Types
There are two types of tokens:
-
Master API Token
Grants full access to your account, including all projects and administrative actions (e.g., add/remove keywords, manage users).
-
Project Auth Token + ViewKey
Provides access to a specific project. Useful when sharing data with third-party tools or restricting access.
Making API Requests
The Keyword.com API follows a RESTful design, using standard HTTP methods:
-
GET to retrieve data
-
POST to create resources
-
PATCH to update data
-
DELETE to remove resources
All responses are returned in JSON format for easy integration.
Base URL
All API requests should be made to:
https://app.keyword.com/api/v2
Rate Limits
API requests are rate-limited per token to protect service stability:
| Endpoint group | Limit |
|---|---|
| Keywords (list, get, create, delete) | 60 requests/minute |
| Competitor history | 30 requests/minute |
| All other endpoints | 60 requests/minute |
429 Too Many Requests. Use exponential backoff (e.g. retry after 1s, then 2s, then 4s) rather than retrying immediately.Pagination
List endpoints return paginated results. Control pagination with query parameters:
| Parameter | Type | Description |
|---|---|---|
page |
integer | Page number (default: 1) |
per_page |
integer | Results per page (default: 20, max varies by endpoint) |
Paginated responses include metadata:
{
"data": [...],
"meta": {
"pagination": {
"total": 150,
"count": 20,
"per_page": 20,
"current_page": 1,
"total_pages": 8
}
},
"links": {
"self": "https://app.keyword.com/api/v2/...&page=1",
"first": "https://app.keyword.com/api/v2/...&page=1",
"next": "https://app.keyword.com/api/v2/...&page=2",
"last": "https://app.keyword.com/api/v2/...&page=8"
}
}
Error Handling
Error responses follow a consistent format with an errors array:
{
"errors": [
{
"code": "401",
"title": "Your request is unauthorized",
"message": "Unauthenticated."
}
]
}
| HTTP Status | Meaning |
|---|---|
401 |
Invalid or missing API token |
403 |
Insufficient permissions (e.g. view-only token) |
404 |
Resource not found |
422 |
Validation error — check the message field for details |
429 |
Rate limit exceeded |
Keyword Update Schedule
One of the core benefits of using Keyword.com is that you don’t need to manually run API requests to keep your keyword data fresh—we handle that for you.
When you add keywords to a project, they’re automatically queued for updates according to your plan. Our system continuously tracks and refreshes keyword rankings in the background, so you can focus on analysis and insights rather than data collection.
Automatic Update Frequency
| Plan Type | Update Frequency |
|---|---|
| Daily | Every 24 hours |
| Weekly | Every 7 days |
Example: If you’re on a weekly plan and added keywords on a Wednesday, your keywords will automatically refresh every Wednesday between 00:00 and 12:00 UTC
This hybrid approach gives you both the convenience of automation and the control of real-time updates when you need them.