Error codes
Messaging API - Error codes
Error registry
Errors use the envelope in Envelope. data is null. The optional error property is field (dotted path), not member.
| HTTP | Code | Meaning | Retry? | Partner action |
|---|---|---|---|---|
| 400 | INVALID_REQUEST | Malformed syntax, unknown request field, invalid identifier, invalid value, empty content, content that is not well-formed UTF-16, unsupported media type, a missing upload file, or an image that contains a QR code. | No | Correct the request before retrying. |
| 400 | INVALID_PAGE_ID | page_id is malformed, expired, or bound to another query. On the reservation-conversation endpoint, any page_id is this error. | No | Start again from the first page with the intended parameters. For older reservation messages, use Get conversation detail. |
| 401 | AUTHENTICATION_REQUIRED | Existing authenticated integration context is absent or invalid. | No | Correct or refresh credentials using the Supply standard. |
| 403 | PROPERTY_ACCESS_DENIED | The authenticated integration lacks current property entitlement. | No | Verify property mapping and entitlement. |
| 403 | CONVERSATION_READ_ONLY | Current conversation policy rejects sending or uploading. | No | Do not send or upload. Continue reading if needed. Recheck access. |
| 404 | RESOURCE_NOT_FOUND | Opaque absent, foreign, hidden, or wrong-scope resource. Also a reservation that is not available for messaging. Also a missing attachment id. After a known upload, attachment metadata or download 404 means the file is still being processed, or it has expired or been deleted. Files are kept for 28 days. | No | Validate the intended property and identifier. Do not probe for existence. After a known upload, retry attachment file_info with bounded backoff until 200, then download. Do not retry other 404s. |
| 409 | RESERVATION_CONVERSATION_CONFLICT | Multiple or incompatible reservation conversations prevent safe selection or creation. | No | Do not repeat the reservation GET blindly. Contact support with meta.ruid. |
| 413 | MESSAGE_TOO_LARGE | The content fails the Message size dual rule, or an uploaded file exceeds 10 MiB. Not used for malformed UTF-16. | No | Reduce or split the text, or send a smaller file, without assuming any server-side truncation. |
| 500 | INTERNAL_ERROR | Unexpected safe failure. | Depends | For reads, retry cautiously. For a send, treat acceptance as unknown unless rejection is proven. |
| 503 | DEPENDENCY_UNAVAILABLE | A required contract fact is unavailable or indeterminate. | Depends | For reads, use bounded exponential backoff and jitter. For send or ambiguous reservation creation, follow Best practices. |
When contacting Agoda Connectivity, include meta.ruid or X-Request-Id, the timestamp, property_id, conversation_id when available, and the exact error code. See Support correlation.
Updated 3 days ago
Did this page help you?

