Authentication

Bearer Token

All requests to the ingest endpoint require a Bearer token in the Authorization header:

Authorization: Bearer <your-token>

Your token is provided during onboarding. If you don’t have one, contact support.

Required headers

Every request must include:

Header	Value
Authorization	Bearer <your-token>
Content-Type	application/json
Accept	application/json

Error responses

HTTP Status	Meaning
401	Authorization header is missing or malformed
403	Bearer token is invalid
500	Server error processing the payload

Common causes of 403

If your token works in tools like Postman but fails from your server:

• Encoding issues — ensure the token is sent as a plain UTF-8 string, not URL-encoded
• Extra whitespace — check for leading/trailing spaces or newlines in the token value
• Proxy interference — some proxies strip or modify the Authorization header. Check your outbound proxy/firewall configuration
• Copy-paste errors — the token may contain special characters like / or = that must be preserved exactly

HTTP response codes

Per the CSN-DTO specification:

• 2xx — accepted, no further action needed
• 3xx — follow the redirect
• 4xx — permanent failure, do not retry
• 5xx — temporary failure, retry after a delay