Skip to Content

Connector signatures are checked against the bytes sent, and bad JSON gets a proper answer

Shipped 2026-10-26

Accented names broke the signature

Connectors sign each request with an HMAC of the body. We checked it against JSON.stringify of the parsed body, which only matches when the sender’s JSON encoder writes every character the way Node does. Accordion’s encoder writes a non-ASCII character as an escape ("José"); Node writes é as raw UTF-8. The bytes differ, so the HMAC differs, and the whole batch was refused with 403 Your token does not match., then refused again on Accordion’s retry.

In the 14 days to 26 October the only four requests whose body contained a non-ASCII character were exactly the four refused this way: 19 October 06:26 UTC (twice) and 25 October (twice). Nothing was stored for 25 October’s delivery.

The signature is now checked against the exact bytes received for every /api/external/ route, the same way the Stripe webhook already worked. A signature over JSON.stringify is still accepted, so no connector that signs that way is affected. The comparison is now constant-time.

A body that isn’t JSON

A malformed body fails inside Express before any of our code, so the sender got an HTML error page, no connector_history row was written, and the only trace was a stack trace logged at info level (seen twice on 26 October at 14:17 UTC, at character 12,828). It now gets 400 { valid: false, message: "Request body is not valid JSON." } (or 413 if too large), and logs http.body_parse_failed at warn with the endpoint, client-id, content length and parse position, never the body.

Last updated on