OverviewPlatformsAPI Reference
Attention

List attention items

What needs a person, newest first: a keyword whose mentions spiked in the last hour (mention.spike), whose negative share of the last 24 hours jumped (sentiment.negative_spike), that turned noisy (keyword.noisy), or a channel whose last sends all failed (channel.failing). Detected once an hour; an item opens when its condition starts and resolves on its own when the condition is gone. Open items by default; `status=all` reads the history. Each opening is also an account event of the same name, which webhook, Slack, email and Telegram channels can subscribe to.

GET
/v1/attention

Authorization

AuthorizationBearer <token>

API key minted via POST /v1/api-keys (format mk_live_...)

In: header

Query Parameters

status?string

open (default), resolved, dismissed, or all.

Default"open"
Value in"open" | "resolved" | "dismissed" | "all"
kind?string

Only these kinds, comma separated: mention.spike, sentiment.negative_spike, keyword.noisy, channel.failing.

limit?integer

Items per page, newest first; 50 by default, at most 100.

Default50
Range1 <= value <= 100
cursor?string

nextCursor from the previous page.

Response Body

application/json

application/json

application/json

curl -X GET "https://api.mentio.dev/v1/attention"
{
  "data": [
    {
      "id": "string",
      "kind": "mention.spike",
      "status": "open",
      "subject": {
        "type": "keyword",
        "id": "string"
      },
      "title": "string",
      "openedAt": "string",
      "resolvedAt": "string",
      "dismissedAt": "string",
      "data": {
        "attentionId": "string",
        "url": "string",
        "keyword": {
          "id": "string",
          "term": "string",
          "kind": "brand",
          "name": "string",
          "groupId": "string"
        },
        "window": {
          "from": "string",
          "to": "string"
        },
        "matches": 0,
        "relevant": 0,
        "baseline": {
          "meanPerHour": 0,
          "stddevPerHour": 0,
          "hours": 0
        }
      }
    }
  ],
  "nextCursor": "string"
}
{
  "error": {
    "code": "unauthorized",
    "message": "string",
    "requestId": "string",
    "retryAfterSeconds": 0
  }
}
{
  "error": {
    "code": "unauthorized",
    "message": "string",
    "requestId": "string",
    "retryAfterSeconds": 0
  }
}

Dismiss an attention item POST

Put an item away. It leaves the open list and does not come back while its condition lasts; once the condition clears, a new episode may open a new item. Idempotent.

Introspect the credential GET

The workspace this credential acts on, how the request authenticated (an API key, an OAuth access token from an MCP sign-in, or the dashboard session), whether it may write, and for a key its id and expiry. Run it first: a read key answers 403 read_only_key on every write, and a wrong workspace is the classic scripting mistake.