Error Handling
HTTP response codes your platform should return and our retry strategy when delivery fails.
Expected HTTP Responses
| Code | Meaning | Action |
|---|---|---|
| 202 | Accepted | Your platform accepted the message — we move on |
| 401 | Unauthorized | Our token expired or is invalid — we will re-authenticate and retry |
| 400 | Bad Request | Payload malformed — logged on our side for investigation |
| 404 | Not Found | Endpoint or match ID not recognized by your platform — we log and skip |
| 500 | Server Error | Your platform returned an error — we retry with exponential backoff |
Retry Strategy
On 401
We refresh the OAuth token and retry the request once
On 5xx
We use exponential backoff (1s, 2s, 4s, 8s…) up to 5 retries
On 4xx (non-401)
We log the error and do not retry (likely a payload issue on our side)
Best Practices
Recommended practices
Return 202 Accepted promptly — process payloads asynchronously if needed
Implement idempotency — messages may be retried on our side
Log all inbound requests and response codes for debugging
Ensure your auth endpoint returns correct token expiry so we can refresh proactively
Set up monitoring for repeated 5xx errors on your receiving endpoints