Celigo · API builder
422 - Unprocessable Content (API builder)
Short answer
A 422 from a Celigo API builder API means the record could not be processed in one of the API steps. Check the pre-mapped log entry, which names the step where the unexpected processing error occurred.
VerifiedLast verified
01Error text
422 - Unprocessable Content
The record cannot be processed. Try again or contact the API publisher.02Likely causes
- Special characters appear in the invoke URL.
- A lookup's output exceeds 5 MB.
- An unexpected processing error occurs in a step such as the response node, pre-map, mapping or post-map.
03How to fix it
- Check the pre-mapped log entry, which names the step where the unexpected processing error occurred.
- Remove special characters from the invoke URL, and keep lookup output under 5 MB.
iNotes
Celigo documents the causes of this response. The steps address each documented cause.
04Official documentation
→Related errors
- 400 - Bad request (API builder)A 400 from a Celigo API builder API means the request payload or URL is not acceptable. Send a correctly formatted JSON payload that is a plain object with a single record.
- 401 - Unauthorized (API builder)A 401 from a Celigo API builder API means the API token is incorrect or missing from the API request header. Send the correct API token in the API request header.
- 404 - Not found (API builder)A 404 from a Celigo API builder API means the request URL does not match any endpoint in scope of the API token, or the API is disabled. Check that the request URL and method match an endpoint that is in scope of the API token.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Celigo work:Open Celigo jobsCeligo rates and salaries