Method not allowed
method_not_allowed
The path exists, but not for this HTTP method. The response carries an Allow header naming the method this endpoint does accept.
Why it happens
A GET where a POST is required, or the reverse — often a URL pasted into a browser address bar, which can only ever issue a GET.
How to fix it
Read the Allow header and use the method it names. The reference lists one per operation.
Safe to retry?
No. The same verb is refused every time — reissue the request with the method the Allow header names.
What it looks like on the wire
{
"type": "https://voicelabs.now/errors/method_not_allowed",
"title": "Method not allowed",
"status": 405,
"detail": "A human-readable explanation of this particular occurrence.",
"instance": "/v1/speech",
"code": "method_not_allowed"
}
Branch on code, never on status or on the prose in detail: two different problems can share a status, and detail is written for humans and may be reworded. Problems a settings page can resolve also carry settings_url, and a scope failure carries required_scope.
Every VoiceLabs API error is an RFC 9457 problem document with a stable code.