HTTP responses
The status codes the gateway returns to your message source.
Last updated October 1, 2026
These are the status codes the gateway returns to your message source. Delivery to your agent is asynchronous — it happens after the response.
Status codes
| Code | Meaning | When |
|---|---|---|
202 | Accepted | Message entered the pipeline. Normal success. Does not mean your endpoint received it yet. |
400 | Bad Request | Invalid JSON, missing body, or nesting depth exceeded. |
401 | Unauthorized | Wrong secret, invalid signature, or replayed nonce. |
403 | Forbidden | Signed slug invalid. The gateway URL was tampered with or copied wrong. |
404 | Not Found | No gateway for this slug. |
410 | Gone | Gateway was deleted. |
413 | Payload Too Large | Body exceeds 512KB. |
503 | Service Unavailable | Internal config error (e.g. secret decryption failed). Message quarantined for replay. |
No 429: rate-limited messages get 202 and go to quarantine. From the caller's perspective, the message was accepted.