OverviewAPI Reference
Company

Get the company profile

What the classifier knows about you: name, description, use cases, your own accounts, and the composed context it reads.

GET
/v1/company

Authorization

AuthorizationBearer <token>

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

In: header

Response Body

application/json

application/json

application/json

curl -X GET "https://api.mentio.dev/v1/company"
{
  "name": "string",
  "description": "string",
  "useCases": [
    "string"
  ],
  "accounts": {
    "x": "string",
    "linkedin": "string"
  },
  "website": "string",
  "competitors": [
    "string"
  ],
  "guidelines": "string",
  "context": "string"
}
{
  "error": {
    "code": "unauthorized",
    "message": "string",
    "requestId": "string",
    "retryAfterSeconds": 0
  }
}
{
  "error": {
    "code": "unauthorized",
    "message": "string",
    "requestId": "string",
    "retryAfterSeconds": 0
  }
}

Update a mention PATCH

The one write on a mention. Set status to ignored or done to handle it (open puts it back), assign it to a workspace member, snooze it out of the feed, leave an internal note, or correct the classifier: `relevant` true or false is your verdict (relevance becomes 100 or 0, and every list, filter, digest and report follows it), `sentiment` replaces the label; null withdraws a verdict and restores the classifier's value. Omitted fields are untouched. Delivery and billing never change.

Update the company profile PATCH

Changing profile fields recomposes the classifier context; setting `context` directly overrides it until the next profile edit. Relevance scores for new mentions follow at once.