POST/api/crm/v1/today/triage

Mark one of the caller's own My day inbox items done, or move it back to the inbox

Personal triage state, not a record write. The user is the verified caller; humans only. attention.done stores the item's signature; the item returns when its signal changes. attention.restore deletes the mark.

App
CRM
Contract
CRM API 9.12.1
Lifecycle
preview
Runtime
restricted
Operation ID
Not declared (legacy exception)
Canonical origin
Not declared; gateway routing required

Purpose and use cases

Mark one of the caller's own My day inbox items done, or move it back to the inbox

The owning App is Vision CRM. CRM owns its records, workflow rules, workspace membership, provenance, and record-level authorization.

Request

POST /api/crm/v1/today/triage

This contract intentionally declares no direct server URL. Obtain the routed App origin before attempting the request.

Authentication and authorization

Send a Vision-issued bearer token for the exact App audience. The token must include the crm entitlement and satisfy the crm workspace required binding.

  • Required scope: crm:today:read

Human roles are not declared in OpenAPI. Record-level and business permission checks remain the owning App's authority.

Headers

  • Authorization: Bearer <access-token> — required.
  • Accept: application/json — recommended where a JSON response is declared.
  • Content-Type: application/json — required for the documented request representation.

Undeclared tracing, idempotency, conditional-request, and version headers are not assumed on this page.

Path and query parameters

This operation declares no path or query parameters.

Request body

Media type: application/json. The body is required.

FieldTypeRulesDescription
schemaVersion"vision-crm-command.v1"requiredNot described in the contract.
commandTypeattention.done | attention.restorerequiredNot described in the contract.
idempotencyKeystringrequired; minimum length 16; maximum length 160Not described in the contract.
keystringrequired; pattern ^[a-z]:[A-Za-z0-9_-]{1,80}$Not described in the contract.
signaturestringoptional; pattern ^[a-f0-9]{64}$Required for attention.done.

Runnable examples

cURL
curl '${APP_BASE_URL}/api/crm/v1/today/triage' \
  --request POST \
  --header 'authorization: Bearer ${ACCESS_TOKEN}' \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "schemaVersion": "vision-crm-command.v1",
    "commandType": "attention.done",
    "idempotencyKey": "<idempotencyKey>",
    "key": "<key>",
    "signature": "<signature>"
  }'
JavaScript (server-side)
const response = await fetch('${APP_BASE_URL}/api/crm/v1/today/triage', {
  method: 'POST',
  headers: {
    authorization: `Bearer ${ACCESS_TOKEN}`,
    accept: 'application/json',
    'content-type': 'application/json',
  },
  body: JSON.stringify({
  "schemaVersion": "vision-crm-command.v1",
  "commandType": "attention.done",
  "idempotencyKey": "<idempotencyKey>",
  "key": "<key>",
  "signature": "<signature>"
}),
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()
Python 3 standard library
import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    '${APP_BASE_URL}/api/crm/v1/today/triage',
    data=json.dumps({"schemaVersion":"vision-crm-command.v1","commandType":"attention.done","idempotencyKey":"<idempotencyKey>","key":"<key>","signature":"<signature>"}).encode(),
    headers={
    "Accept": "application/json",
    "Authorization": "Bearer <ACCESS_TOKEN>",
    "Content-Type": "application/json"
},
    method='POST',
)
with urllib.request.urlopen(request, timeout=30) as response:
    result = json.load(response)

The current TypeScript reference client covers Platform token exchange and core reads. No native SDK helper is declared for this operation; use the HTTP contract directly and follow the SDK guidance.

Responses

StatusMeaningSchema
200The item's triage state after the commandobject
400The request is invalidobject
401Authentication is missing or invalidobject
403The authenticated actor lacks the CRM capability or workspace bindingobject
503The CRM dependency or authenticated API configuration is unavailableobject

Success response schema

FieldTypeRulesDescription
schemaVersion"vision-crm-triage-result.v1"requiredNot described in the contract.
keystringrequiredNot described in the contract.
stateinbox | donerequiredNot described in the contract.
200 illustrative response
{
  "schemaVersion": "vision-crm-triage-result.v1",
  "key": "<key>",
  "state": "inbox"
}

Errors and troubleshooting

Error bodies and codes are shown only where the approved contract declares them. Use status, the declared error schema, and any correlation identifier returned by the App; do not infer that two Apps share one envelope.

  • 400 — The request is invalid
  • 401 — Authentication is missing or invalid
  • 403 — The authenticated actor lacks the CRM capability or workspace binding
  • 503 — The CRM dependency or authenticated API configuration is unavailable

Collection behavior

Pagination: not declared. Filtering/search: not declared. Sorting: not declared.

Cursor lifetime, cursor binding, stable ordering, maximum traversal, and unknown-filter behavior are not assumed unless stated by a parameter description or schema constraint above.

Operational behavior

  • Rate limit: No operation-specific limit or 429 response is declared.
  • Retry: Retry only when the documented error model or response headers authorize it. Timeout and backoff values are not declared by this operation.
  • Idempotency: No idempotency header or replay window is declared.
  • Concurrency: No ETag, If-Match, or optimistic-version header is declared.

Security and privacy

  • Keep client credentials and bearer tokens on trusted servers.
  • Send only to the exact approved HTTPS origin and audience.
  • Treat response data according to the owning App's classification and retention policy; the OpenAPI contract does not itself grant data access.
  • Do not log credentials, tokens, complete private payloads, or secrets.

Edge cases and known documentation gaps

  • No stable operation ID (legacy exception).
  • No direct server URL; gateway routing is unresolved here.
  • The request body has no purpose or conditional-rule description.
  • Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.

Contract history and evidence