Create a webhook
Subscribes a URL to one or more events (REST-hook style, as used by Zapier, Make and Power Automate). Unknown event names are dropped; the response shows the events that were kept. Store the returned signing_secret to verify deliveries.
Authentication
OAuth 2.0 Client Credentials Flow. To obtain an access token:
-
Request API credentials from HINDSITE support to receive your
client_idandclient_secret -
Make a POST request to obtain an access token:
POST https://app.hindsiteind.com/oauth/token
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET
- The response will contain your access token:
{
"access_token": "your_access_token_here",
"token_type": "Bearer",
"expires_in": 7200,
"created_at": 1234567890
}
- Include the token in subsequent API requests:
Authorization: Bearer your_access_token_here
Request
Event names from List subscribable events. Unknown names are ignored.
Optional label. Defaults to API subscription.
Response
Label shown in Settings › Webhooks.
Inactive webhooks receive no deliveries. A webhook is deactivated automatically after sustained delivery failures and can be reactivated in Settings › Webhooks.
Event names this webhook receives, from List subscribable events.
HMAC-SHA256 key for the X-Webhook-Signature header on every delivery.
