Workato · Webhooks

400 Bad Request on webhook events

Short answer

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

Workato error
400 Bad Request

02Likely 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

  1. Verify that the payload the sender posts matches the Webhook type set on the trigger.
  2. For payloads with non-UTF-8 characters, choose the Raw Binary Data option under Webhook Type.
  3. 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

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

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.