Skip to content
Fix

JotForm webhooks ship with the right Content-Type

JotForm's webhook receiver rejects `application/json` bodies. The Tiny Command SDK now respects the requested Content-Type and sends `application/x-www-form-urlencoded` when JotForm asks for it.

JotForm's registration endpoint always returned `WebHook URL is wrong` even when the URL was clearly valid. The cause: our SDK was sending JSON when JotForm expects form-urlencoded.

Now: the SDK's `registerTrigger` honors per-app Content-Type configuration. Other apps with non-JSON registration APIs benefit too.