Every request to the SERPtag REST API must include a valid API key. Requests without authentication, or with an invalid API key, will return a 401 Unauthorized response.

Base URL https://serptag.com/api

Before making your first request, create an API key from Settings → API Keys.

Create an API Key

If you haven’t already created an API key, follow the Create an API Key guide. Your API key will look similar to:

sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

To use the REST API, you’ll need:

An Agency or Enterprise subscription (2,500+ keywords)
An active SERPtag account
A valid API key

Authentication Methods

The REST API supports two authentication methods.

X-API-Key (Recommended)

The recommended authentication method is to send your API key using the X-API-Key request header.

X-API-Key: sk_live_your_key_here

Bearer Token

You can also authenticate using the standard Authorization header.

Authorization: Bearer sk_live_your_key_here

Both methods provide the same level of access.

Making Your First Request

Once you’ve created your API key, you’re ready to make your first request.

Using X-API-Key

curl -H "X-API-Key: sk_live_your_key_here" \
https://serptag.com/api/projects/

Using a Bearer Token

curl -H "Authorization: Bearer sk_live_your_key_here" \
https://serptag.com/api/projects/

If authentication succeeds, the API will return your SERPtag projects as a JSON response.

Code Examples

Below are examples in some of the most common programming languages.

JavaScript

const response = await fetch("https://serptag.com/api/projects/", {
  headers: {
    "X-API-Key": "sk_live_your_key_here"
  }
});

const data = await response.json();

console.log(data);

Python

import requests

response = requests.get(
    "https://serptag.com/api/projects/",
    headers={
        "X-API-Key": "sk_live_your_key_here"
    }
)

print(response.json())

Authentication Requirements

Every request is validated before data is returned.

Requirement	Details
API Key	Must be valid and active
Key Format	Begins with `sk_live_`
Subscription	Agency or Enterprise
Plan Size	2,500+ tracked keywords

Using the Same API Key with MCP

The same API key works across both SERPtag services.

Service	URL
REST API	`https://serptag.com/api`
SERPtag MCP Server	`https://mcp.serptag.com/mcp`

You don’t need to create separate API keys for MCP and the REST API.

Security Best Practices

To keep your account secure, we recommend following these guidelines.

✅ Do

Store API keys in environment variables.
Keep your API keys in a secure password manager.
Rotate API keys if they have been exposed.
Only share API keys with trusted team members.

❌ Don’t

Commit API keys to Git repositories.
Embed API keys in frontend applications.
Share API keys publicly.
Send API keys in screenshots or emails.

Common Authentication Errors

Status Code	Meaning	Solution
401 Unauthorized	Missing or invalid API key	Verify the full `sk_live_...` key has been copied correctly.
403 Forbidden	You don’t have permission to access the requested resource	Confirm the project or keyword belongs to your account.
429 Too Many Requests	Rate limit exceeded	Wait for the limit to reset or reduce the number of requests.

Rate Limits

Each API key includes generous usage limits.

Limit	Value
Requests	1,000 requests per hour

The hourly limit is shared across both the SERPtag REST API and the SERPtag MCP Server.

​Create an API Key

​Authentication Methods

​X-API-Key (Recommended)

​Bearer Token

​Making Your First Request

​Using X-API-Key

​Using a Bearer Token

​Code Examples

​JavaScript

​Python

​Authentication Requirements

​Using the Same API Key with MCP

​Security Best Practices

​✅ Do

​❌ Don’t

​Common Authentication Errors

​Rate Limits