Skip to main content
The TruAgents public API reports failures with standard HTTP status codes and a JSON error envelope. Per-API status-code tables live on the API pages themselves — the sections below point you at the canonical detail.

​
OAuth token endpoint

POST /oauth/token returns standard OAuth 2.0 error envelopes per RFC 6749 §5.2 with the codes invalid_request, invalid_client, and invalid_grant. See Authentication → Error responses for the full table and remediation notes.

​
Unsubscribe API

/api/v1/unsubscribe/{email,sms,phone} returns 400, 401, 403, or 429 with the shared RestErrorResponse envelope (described below). See Unsubscribe API → Error responses for status codes, sub-codes (bad_request, invalid_cursor, unauthorized_organization), and per-endpoint failure modes.

​
Response body shape

REST API endpoints share this JSON envelope:
Program against error — it is stable and machine-readable. Log message for humans; its wording may change without notice. POST /oauth/token uses the RFC 6749 §5.2 envelope instead — error plus error_description. See Authentication → Error responses for the OAuth-specific shape.