Workato · Webhooks
400 Bad Request on webhook events
A webhook event sent to Workato gets a 400 Bad Request when its payload does not match the Webhook type configured on the trigger, or is not UTF-8 compatible. Match the Webhook type to the payload, or use Raw Binary Data for non-UTF-8 content.
VerifiedLast verified
01Error text
400 Bad Request02Likely causes
- The payload is not valid JSON for the configured Webhook type.
- A JSON, Form or XML payload is not UTF-8 compatible.
03How to fix it
- Verify that the payload the sender posts matches the Webhook type set on the trigger.
- For payloads with non-UTF-8 characters, choose the Raw Binary Data option under Webhook Type.
- Send the event again and confirm it is accepted.
iNotes
Webhook trigger errors do not create a job, so there is no job ID or job history entry. They appear only on the logging service page.
04Official documentation
→Related errors
- Error generating schema for responseError generating schema for response appears in Workato's webhook setup when the Content-Type header of the webhook does not match its payload. Have the sender fix the format, or skip the guided setup and define the payload schema manually.
- 429 Too Many Requests (webhook gateway)Workato's webhook gateway returns 429 Too Many Requests when incoming webhook events exceed both the steady rate and the burst allowance. The sender should retry the webhooks until they are accepted, using the Retry-After header.
- 400 Bad RequestA 400 Bad Request error in Workato means the external server could not process the request because it is malformed or invalid. Check field names, required values, record IDs and file sizes in the failing step, then reconnect the app.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer