method_not_allowed
- HTTP status
- 405
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- No
Method not allowed. The path exists but not with this method. The Allow response header lists the supported methods.
What it means
The API returns HTTP 405 with error.code set to method_not_allowed. The default message is: "This route does not support that HTTP method."
Common causes
- PUT sent where the API uses PATCH.
- DELETE sent to a resource that cannot be deleted.
How to identify it
Check the response status (405) and error.code (method_not_allowed). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.
How to fix it
- Use a method listed in the
Allowheader.
Retry guidance
Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
Nothing was done and nothing was stored (under an Idempotency-Key, if you sent one), so the request can be sent again, with the same key if you used one, once the cause is fixed.
Who can fix it
The developer who sends the request can fix it; no administrator action is normally needed.
When to contact support
If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).
Example error response
JSON
See all codes in the error-code reference.