After the order
Record protection as Teak issues and changes it, and give the customer their protection details.
Teak sends signed webhooks to your server when protection is issued, and whenever it changes afterwards, for example when a customer voids it or files a refund request.
1. Choose the events you need
Every event is asynchronous: it arrives after the change, usually within about two minutes, not in the response to a call. Subscribe to the required events, and to any others your team acts on.
| Events | When Teak sends them | What you do |
|---|---|---|
| Contract Issued | Teak issues protection for an item, once per item. | Record the protection against your order. Required. |
| Contract Void | Protection is removed: the customer voids it within its look period, or the order doesn't pass Teak's checks. | Refund the customer the protection price. Required. |
| Contract Canceled, On Hold, Chargeback | Protection is canceled, paused, or disputed. | Update the protection's status in your system. Don't refund a cancellation. |
| Contract Upgraded, Downgraded, Exchanged | An item changes after purchase, for example an exchange. | Update the protection and its price. Downgraded is required if customers can exchange items. |
| Refund request events | A customer files a refund request, and as Teak reviews and decides it. | Keep your support team informed. |
2. Set up your endpoint
Set up an HTTPS endpoint and your subscriptions in the Teak Dashboard, following Receiving webhooks. Verify every request's signature, as described in Verifying signatures.
3. Record issued protection
Teak issues a contract for each protected item and sends a Contract Issued webhook for each one. Use it to record the protection against your order and to reconcile your invoice. A trimmed example:
{
"resource": "Policy",
"action": "Issued",
"data": {
"status": "issued",
"product": "Refund Protection",
"item_name": "Summer Fest - General Admission",
"reference_number": "ITEM-1",
"policy_number": "4f527d2e-0053-4b1c-82dd-db095f09e743",
"order_number": "ORD-1001",
"protecht_order_id": "3f1c9a2e-8b4d-4e6f-9a0b-1c2d3e4f5a6b",
"premium": "4.60",
"currency": "USD",
"issued": "2026-05-09T22:29:19.106Z",
"updated": "2026-05-09T22:29:19.106Z"
}
}| Webhook field | Use it to |
|---|---|
order_number | Find your order. It's the order number you sent when you confirmed the order. |
reference_number | Find the item. It's the reference_id you sent for the item to the Programs API. |
policy_number | Identify the contract, for voids and support. |
premium | Check it matches the protection price you charged. |
protecht_order_id | The session ID the order was placed on, which is also the Teak order ID. |
See Contract events for every field.
If Contract Issued hasn't arrived within a few minutes, look the order up with Retrieve order details.
4. Give the customer their protection details
Who tells the customer depends on the protection:
| Protection | Teak's email | What you do |
|---|---|---|
| Optional | Teak emails the customer their protection details, with links to the terms, a refund request, and cancellation. | Optionally, mention the protection in your own confirmation. |
| Embedded | Teak doesn't email the customer. | Send the customer their protection details yourself, in your confirmation or a separate message. |
Get the links for each contract with Retrieve order details once Contract Issued arrives:
Next steps
Your integration is complete in sandbox. Next:
- Go live: run the checklist and UAT cases, then switch to production.
- See every field in the contract events and refund request events.
Updated 9 days ago
