Webhook Ingestion
Webhook ingestion provides a simplified entry point into the Data Ingest API for external systems that support outbound webhooks.
For full documentation on webhook payloads, authentication, item ID selection, and examples, see Webhooks in Data Connectivity.
Quick Reference
POST /api/webhook/{stream}
Authorization: Bearer ik_<key_id>_<secret>
Content-Type: application/json
{
"key": "value",
"nested": {
"field": "stored as raw JSON"
}
}Response: 202 Accepted
Configuring External Systems
When setting up a webhook in an external system, you need:
| Setting | Value |
|---|---|
| URL | https://inspire.yourcompany.com/api/webhook/{stream} |
| Method | POST |
| Content-Type | application/json |
| Authentication | Bearer token — your Inspire ik_<key_id>_<secret> ingest credential |
Signature Verification
Connectors can optionally require HMAC-SHA256 signature verification by configuring a Webhook Signing Key. When set, every request must include:
| Header | Description |
|---|---|
X-Webhook-Signature | sha256=<hex> — HMAC-SHA256 of timestamp.body |
X-Webhook-Timestamp | Unix epoch seconds (must be within 5 minutes of server time) |
For full details, signing examples, and code samples, see Signature Verification in Data Connectivity.
Common Integrations
| System | Webhook Support |
|---|---|
| GitHub | Repository events, CI/CD status |
| Slack | Slash commands, event subscriptions |
| Zapier | Any Zapier-supported trigger |
| Microsoft Power Automate | HTTP action |
| IFTTT | Webhooks service |
| Jira | Issue events |
| PagerDuty | Incident events |
Each of these systems can POST JSON data to your Inspire webhook endpoint. Configure the authentication header with your ingest key.
Last updated on