You can Create and Delete webhooks through our Dashboard. We are working to expand this feature, so stay tuned for updates.
Attribute | Type | Description |
|
| The type of Event. Can be from any of the event type list (see below). |
|
| The URL to call when the Webhook is triggered. |
|
| A SHA-256 secret used to secure the Webhook communication. |
|
| Sets if related Event is dispatched. Default is |
|
| Whether the Webhook is deleted. Default is |
|
| Whether the Webhook endpoint is verified. Default is |
Changes since API version 2019-02-01
We are deprecating the old headers, which means it is not a breaking change but it's recommended to update them as soon as possible.
X-Share-Webhook-Signature
becomes X-BuiltOn-Webhook-Signature
X-Share-Webhook-Type
becomes X-BuiltOn-Webhook-Type
Key | Description |
| Verifies that the incoming requests are legitimate, you should hash the response body with the SHA-256 secret and verify that it matches the |
| Two types that describe the nature of the webhook:
|
| How many times BuiltOn tried to send a webhook to your endpoint. BuiltOn will try to send 5 times. After the limit is reached, the retrying process will stop. |
HTTP/1.1 200 OKContent-Type: application/jsonX-BuiltOn-webhook-Type: WebhookMessageX-BuiltOn-webhook-Signature: 02d522b33c34e0655e8a97c49b5d038a2abd93cb86f4608b9e7febe0e28acf64X-BuiltOn-Event-Retries: 0{"object_type":"machine_learning_model","previous_data":{"training_status":"CREATED"},"kind":"machine_learning_model.runnable","object":{"evaluation":{},"human_id":"XL3R47","deleted":false,"training_status":"RUNNABLE","created":1565770053099,"modified":1565770059308,"company":"5ce68495873a43000d3a0d1c","_id":"5d53c1451a7e86000fd0d852"},"url":"https://enf38z1loomb1zg.m.pipedream.net/"}
Go to the Webhooks and click New webhook +.
FIll in the event_type
and the endpoint
.
Go use your new webhook.
Attribute | Type | Description |
|
| The type of Event. |
|
| The URL to call when the webhook is triggered. |
Go to Webhooks and click the webhook you want to delete. You should see 'Delete webhook' below its details.
Click the X and confirm you want to delete it.
Mourn your deleted webhook.
Event Type | Description |
| Order created |
| Order updated |
| Order cancelled |
| User created |
| User updated |
| User deleted |
| Subscription created |
| Subscription updated |
| Subscription deleted |
| Subscription activated |
| Subscription postponed |
| Subscription completed |
| Subscription stopping the next cycle |
| Subscription cancelled |
| Payment created |
| Payment updated |
| Payment deleted |
| Payment succeeded |
| Payment processing |
| Payment failed |
| Payment captured |
| Payment cancelled |
| Payment pending |
| Payment requires an authentication action |
| Product created |
| Product updated |
| Product deleted |
| Plan created |
| Plan updated |
| Plan deleted |
| ML model created |
| ML model training is ready to start |
| ML model is starting the training process |
| ML model has started and is currently being training |
| ML model has failed to train |
| ML model succeeded the training process |
| ML model couldn't start the training process, because there is no sufficient data |
| ML model evaluation is available |
Body Parameters | Type | Description |
|
| The type of event to receive information about. |
|
| The URL to call when the Webhook is triggered. |
|
| Sets if related Event is dispatched. Default is |
POST /webhooks HTTP/1.1Content-Type: application/jsonAuthorization: Bearer <service-account-key>X-Builton-Api-Key: <builton-api-key>Host: api.builton.dev{"endpoint": "http://requestbin.fullcontact.com/asdfasdf","event_type": "order.created"}
HTTP/1.1 200 OKContent-Type: application/json{"_id": {"$oid": "5964a0ead57ba2036750a3b4"},"company": {"$oid": "57ee9c71d76d431f8511142f"},"created": {"$date": 1499767018360},"updated": {"$date": 1499767018360},"event_type": "order.created","deleted": false,"secret": "ed06e2f4e7bdb5ee6050695aba5ed3f2725fd3394df22f3a8a0c2856123a","endpoint": "http://requestbin.fullcontact.com/1o2mfpb1","verified": false,"active": true}
The Webhook has to be verified before related data on related Events are dispatched. The API tries to verify the endpoint when the Webhook is created. If the endpoint returns an HTTP status code 2XX then the Webhook is set to verified
.
If an endpoint is updated, then the Webhook is not verified anymore. It is possible to manually try to verify the endpoint by doing the following request.
Body Parameters | Type | Description |
|
| ID of the webhook to be verified. |
POST /webhooks/5964a0ead57ba2036750a3b4/verify HTTP/1.1Content-Type: application/jsonAuthorization: Bearer <service-account-key>X-Builton-Api-Key: <builton-api-key>Host: api.builton.dev
HTTP/1.1 200 OKContent-Type: application/json{"_id": {"$oid": "5964a0ead57ba2036750a3b4"},"company": {"$oid": "57ee9c71d76d431f8511142f"},"created": {"$date": 1499767018360},"updated": {"$date": 1499767018360},"event_type": "order.created","deleted": true,"secret": "ed06e2f4e7bdb5ee6050695aba5ed3f2725fd3394df22f3a8a0c2856123a","endpoint": "https://www.google.com","verified": true,"active": true}