MuleSoft · APIkit for REST

APIKIT:NOT_ACCEPTABLE

Short answer

APIKIT:NOT_ACCEPTABLE is the APIkit for REST error type that maps to HTTP status 406 with the response message "Not acceptable". 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

MuleSoft error
Error type: APIKIT:NOT_ACCEPTABLE

HTTP status: 406
Response message: Not acceptable

02Likely causes

  • Unconfirmed: the request's Accept header asks for a media type the API specification does not define for that response.
  • APIkit for REST automatically validates incoming requests against the API contract defined in RAML or OAS.

03How to fix it

  1. Check the Accept header of the request against the response media types the API specification defines.
  2. Compare the failing request with the API specification the APIkit router uses, and correct whichever of the two is wrong.
  3. To control what the caller receives, add an On Error Propagate handler with the type APIKIT:NOT_ACCEPTABLE that sets the response body and an httpStatus variable of 406.
  4. Adapt the handler if your API needs a custom status code or message.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.