Content Integration errors use a stable error.code value. Treat the code as the client-facing contract and the message as human-readable detail.

Error codes

Code	Meaning	Retry
`content_invalid_api_key`	Bearer token is missing, malformed, revoked, or expired.	No. Create or rotate the key.
`content_invalid_request`	Request body failed validation.	No. Fix the payload.
`content_forbidden`	Signed-in admin cannot manage the target organization.	No. Use an admin with access.
`content_not_found`	Job, key, or webhook was not found.	No, unless the id was mistyped.
`content_conflict`	Request conflicts with an existing state.	Usually no. Check idempotency.
`content_rate_limit_exceeded`	Key rate limit was exceeded.	Yes, after waiting.
`content_internal_error`	Unexpected server error.	Yes, with backoff.

Example error

{
  "error": {
    "code": "content_invalid_api_key",
    "message": "Invalid or missing Content Integration API key",
    "status": 401
  }
}

Retry 429 after waiting at least 30 seconds.
Retry 500 with exponential backoff.
Do not retry 400 without changing the payload.
Do not retry 401 without replacing the key.
Do not create a second job for the same source content while the original job is still queued or processing.

When a job reaches failed, fetch the result endpoint and inspect:

Fix the source JSON or requested outputs, then create a new job with a new idempotency key if the source content changed.

Send these fields to TutorFlow support:

Field	Notes
`jobId`	Required for expansion issues.
`keyPrefix`	Safe to share. Do not send the full key.
Endpoint path	Example: `/v1/content/integrations/expansions`.
Timestamp	Include timezone.
Idempotency key	Helps find duplicate or retried requests.
Final response body	Include error object and status code.
Source JSON sample	Include only if it can be shared.