Developer reference
Good data. A clear interface.
A reference layout for search data and API integrations. Explore example requests, response structures and connection patterns.
Documentation template: the endpoints and responses below are illustrative, not a published API contract. Contact the team for an integration’s actual specifications.
Quick start
Select a language to explore the same example request. Copying a snippet does not send a request.
{
"domain": "example.com",
"organic_keywords": 1284,
"visibility": 78.4,
"meta": { "example": true }
}Local sample only. No network request was made.
Authentication
The example uses a bearer token placeholder. Actual credentials, permissions and authentication requirements are agreed for each integration.
Authorization: Bearer YOUR_API_KEY Content-Type: application/json
Example endpoints
A sample resource structure for a search intelligence interface.
| METHOD | RESOURCE | Purpose |
|---|---|---|
| GET | /v1/domain/overview | Overview |
| GET | /v1/keywords | Keyword intelligence |
| GET | /v1/rankings | Rank tracking |
| GET | /v1/backlinks | Backlinks |
Responses
Use predictable data structures and clear error handling when planning your integration. The example below shows a validation error.
{
"error": {
"code": "INVALID_DOMAIN",
"message": "Provide a valid domain name."
}
}