Celigo · API builder
400 - Bad request (API builder)
Short answer
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.
VerifiedLast verified
01Error text
400 - Bad request02Likely causes
- The payload JSON format is incorrect.
- Special characters appear in the invoke URL.
- The payload is not a plain object. A single record is supported in the payload.
- The request URI length exceeds the limit.
03How to fix it
- Send a correctly formatted JSON payload that is a plain object with a single record.
- Remove special characters from the invoke URL and shorten the request URI.
iNotes
Celigo documents the causes of this response. The steps address each documented cause.
04Official documentation
→Related errors
- 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.
- 413 - Payload too large (API builder)A 413 from a Celigo API builder API means the API request is larger than 5 MB. Keep the API request at 5 MB or less.
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