post · mentions:write

Save a view

Save a view

Write

REST

post/api/v1/views
curl "https://herculeradar.com/api/v1/views" \
  --request POST \
  --header "Authorization: Bearer hr_live_…" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: $(uuidgen)" \
  --data '{"name":"Acme"}'

MCP

Tool name create_mention_view. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

Save the current filter object under a name. Same shape as the mentions query string.

Request body

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "filters": {
      "type": "object"
    }
  }
}

Response

{
  "data": {
    "id": "uuid",
    "name": "Urgent complaints"
  },
  "meta": {
    "capability": "create_mention_view",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/create_mention_view"
  }
}

Authorization

Requires the mentions:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.

Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.