API keys
API keys are generated in the Mentova dashboard under Settings → API. Keys are prefixed with mtv_live_ followed by 32 hex characters.
Each key is shown only once at creation time. Store it securely - if lost, delete the key and generate a new one.
Sending the key
Include the key in every request using either of these headers:
# Preferred
X-API-Key: mtv_live_your_key_here
# Alternative
Authorization: Bearer mtv_live_your_key_here
Both headers are accepted. If both are present, X-API-Key takes priority.
Example request
curl https://mentova.ai/api/v1/brands \
-H "X-API-Key: mtv_live_your_key_here"
Plan requirement
API keys are only valid for Agency plan accounts. Any key belonging to a lower-tier account returns:
{
"error": "API access requires Agency plan",
"code": "PLAN_REQUIRED"
}
HTTP status: 403.
Rate limiting
Each key is limited to 60 requests per minute. Exceeding this limit returns HTTP 429 with a Retry-After: 60 header. The rate limiter fails open - if Redis is unavailable, all requests are allowed through.
{
"error": "Rate limit exceeded",
"code": "RATE_LIMITED"
}
Error responses
| HTTP | code | Cause |
|---|---|---|
401 | MISSING_API_KEY | No key provided in the request |
401 | INVALID_API_KEY | Key not found or revoked |
403 | PLAN_REQUIRED | Account is not on the Agency plan |
429 | RATE_LIMITED | 60 req/min exceeded |