Skip to main content
Every non-2xx response uses a consistent JSON format. Classify errors by stable error.code, not the human-readable message.

Error response format

details is optional and machine-readable. Unknown detail fields should be ignored.

Request correlation

Every response includes an X-Request-Id header, and error bodies repeat it as error.request_id. Log that identifier with the failed operation and provide it to Brightalk support. Do not log API keys or full contact data. You may send X-Request-Id using 1–64 characters from A-Z, a-z, 0-9, ., _, :, or -. Brightalk replaces a missing or invalid value with a generated identifier.

Authentication distinctions

These responses describe credential usability without revealing resources belonging to another organization.

Status and error catalog

A known path with an unsupported method also includes Allow. Retry-After appears where waiting before another attempt is meaningful. Error responses never expose implementation names, private payloads, query details, or stack traces.