MuleSoft · APIkit for REST
APIKIT:NOT_IMPLEMENTED
Short answer
APIKIT:NOT_IMPLEMENTED is the APIkit for REST error type that maps to HTTP status 501 with the response message "Not implemented". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
Needs verificationLast reviewed
Needs verification. The error type, its HTTP status code and its response message are confirmed in the APIkit error handling reference. The documentation pages checked do not state exactly which request condition raises this type, so the causes below are not confirmed. Treat it as a starting point, not as a confirmed fix.
01Error text
Error type: APIKIT:NOT_IMPLEMENTED
HTTP status: 501
Response message: Not implemented02Likely causes
- Unconfirmed: the API specification defines the resource and method, but the application has no flow that implements it.
- APIkit for REST automatically validates incoming requests against the API contract defined in RAML or OAS.
03How to fix it
- Check that the application has a flow for the resource and method named in the request.
- 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:NOT_IMPLEMENTEDthat sets the response body and anhttpStatusvariable of 501. - Adapt the handler if your API needs a custom status code or message.
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:METHOD_NOT_ALLOWEDAPIKIT: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.
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