MuleSoft · APIkit for REST
APIKIT:METHOD_NOT_ALLOWED
APIKIT:METHOD_NOT_ALLOWED is the APIkit for REST error type that maps to HTTP status 405 with the response message "Method not allowed". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
Needs verificationLast reviewed
01Error text
Error type: APIKIT:METHOD_NOT_ALLOWED
HTTP status: 405
Response message: Method not allowed02Likely causes
- Unconfirmed: the resource exists in the API specification, but not with the HTTP method the request used.
- APIkit for REST automatically validates incoming requests against the API contract defined in RAML or OAS.
03How to fix it
- Check which HTTP methods the API specification defines for the requested resource.
- Compare the failing request with the API specification the APIkit router uses, and correct whichever of the two is wrong.
- To control what the caller receives, add an On Error Propagate handler with the type
APIKIT:METHOD_NOT_ALLOWEDthat sets the response body and anhttpStatusvariable of 405. The APIkit scaffolder can generate this baseline handler. - Adapt the handler if your API needs a custom status code or message.
iNotes
The APIkit router has attributes that change what it validates: queryParamsStrictValidation (validates that request query parameters are defined in the RAML file), headerStrictValidation (validates that request headers are defined in the RAML file or belong to a well-known set of headers) and disableValidations (disables validations of requests).
04Official documentation
→Related errors
- APIKIT:NOT_FOUNDAPIKIT:NOT_FOUND is the APIkit for REST error type that maps to HTTP status 404 with the response message "Resource not found". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- APIKIT:BAD_REQUESTAPIKIT:BAD_REQUEST is the APIkit for REST error type that maps to HTTP status 400 with the response message "Bad request". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer