Sources overview
A source is any service that sends you webhooks.
How sources work
Each source is given a unique Hookdeck URL that can be pasted into the webhook URL field of the sender platform. Once your provider is sending webhooks to a Hookdeck URL, events are ingested and routed according to your connection rules.
Content-types
Hookdeck aims to be compatible with every API provider. To accomplish this, we remain platform-agnostic and ingest any inbound requests (up to 10 MiB) with one of the following content-types:
text/plaintext/xmlapplication/jsonapplication/x-www-form-urlencodedapplication/xmlapplication/*+jsonapplication/jwtmultipart/form-data
If you encounter a problem integrating a specific API provider, send us a message.
Custom methods
Some providers send webhooks in non-POST methods, e.g. PUT, PATCH, DELETE or even GET. GET requests are not accepted by default, but you can enable them explicitly by using a x-hookdeck-allow-methods query string parameter in your Hookdeck source URL
?x-hookdeck-allow-methods=get
Custom responses
Some API vendors modify their behavior based on the response they receive from a webhook. For these providers, Hookdeck supports setting custom responses through the use of the query string parameter x-hookdeck-response.
Append one of the following query parameters to the Hookdeck-provided source URL to achieve the desired response.
| Response | Query parameter example | Behavior |
|---|---|---|
| Empty | ?x-hookdeck-response=null or ?x-hookdeck-response | Hookdeck responds with an empty body |
| Text | ?x-hookdeck-response[text]=Hello+World | Hookdeck responds with the text Hello World |
| JSON | ?x-hookdeck-response[json]=%7B%22message%22%3A%22Hello%20World%22%7D | Hookdeck responds with the specified JSON |
| XML | ?x-hookdeck-response[xml]=<root><child></child></root> | Hookdeck responds with the specified XML |
Handshakes and validation
Some API providers require a validation step, known as a "handshake" or "challenge." While this is not standard across all providers, we do our best to implement validation for any platform that our users integrate with.
At this time, we've implemented handshake support for the following platforms:
- Adobe Acrobat Sign
- Adyen
- Asana
- Google Business Messages
- helloflex.com
- HelloSign
- Infusionsoft
- Mailchimp
- monday.com
- Nylas
- Okta
- OnFleet
- Oura
- Slack
- Smartsheet
- Strava
- Trello
- Twitch
- Twitter (must use our Twitter integration)
- Zoom (must use our Zoom integration)
- Wallester
- WebSub generic integration
- REST Hooks implementation
If your provider requires a handshake and is missing from this list, contact us and we will add support within 24 hours.