Developer documentation
Integrate Mentiontone into your own tools via the REST API, outgoing webhooks, or an MCP server for AI assistants.
Quickstart
- Open Team settings → API keys → New key and name it.
- Copy the generated key (it starts with
mt_api_). - Call the mentions endpoint with the key in the
Authorizationheader.
Your first call:
curl https://mentiontone.com/api/v1/mentions \ -H "Authorization: Bearer mt_api_your_key_here"
Authentication
Every request carries a bearer token in the Authorization header.
Each key belongs to exactly one team, so the team is implied by the key and never appears in the URL.
Authorization: Bearer mt_api_xxxxxxxxxxxxxxxxxxxxxxxx
- Create, reveal, and revoke keys in Team settings → API keys.
- A revoked key stops working immediately and returns
401. - Keys are scoped to your team's data only.
Rate limits & errors
Requests are limited to 60 per minute per key. Over the limit you get
429 with a Retry-After header.
Errors use a consistent envelope:
{
"error": {
"code": "unauthorized",
"message": "Missing, invalid, revoked, or expired API key."
}
}
| Status | code | Meaning |
|---|---|---|
| 400 | bad_request | Invalid parameter (e.g. malformed cursor or since). |
| 401 | unauthorized | Missing, invalid, revoked, or expired key. |
| 429 | rate_limited | Too many requests; retry after 60 seconds. |
Mentions
GET /api/v1/mentions returns your team's mentions, newest first.
Page with the opaque cursor returned in next_cursor; filter with
source, platform,
alert_id, and since. Up to limit (max 100) per page.
curl "https://mentiontone.com/api/v1/mentions?source=alert_match&limit=50" \ -H "Authorization: Bearer mt_api_your_key_here"
See the full schema, every field, and a live "try it" client in the API reference.