Receive credit webhook events

React to allowance and credit-capacity changes in an approved preview environment. You need a registered webhook endpoint and confirmation that credit events are enabled for your workspace.

Events

Event	Meaning
`isv.credits.allowance.changed`	A current or scheduled allowance changed
`isv.credits.allowance.paused`	The current allowance was paused
`isv.credits.allowance.resumed`	The current allowance was resumed
`isv.credits.allowance.expired`	The allowance period ended
`isv.credits.company.threshold`	Committed company usage crossed 80% of its allowance
`isv.credits.company.exhausted`	Company allowance availability reached zero
`isv.credits.pool.low`	Pool availability crossed 20% or 10% remaining
`isv.credits.pool.exhausted`	Pool availability reached zero
`isv.credits.consumption.reversed`	Finalized consumption was reversed
`isv.credits.bulk.completed`	A bulk allowance job finished, possibly with row errors

Committed usage includes finalized usage and active reservations. The 20% and 10% pool notifications are distinct events; do not combine their identifiers.

Read the payload

Example pool threshold eventjson

{
  "eventId": "isv-credit:example-pool-threshold-20",
  "data": {
    "id": "isv-credit:example-pool-threshold-20",
    "type": "isv.credits.pool.low",
    "timestamp": "2026-09-22T10:00:00.000Z",
    "data": {
      "schemaVersion": "1.0",
      "triggeringCompanyId": "66b9f0a1c2d3e4f567890123",
      "reservationId": "example-reservation-142",
      "totalCredits": 10000,
      "availableCredits": 1900,
      "percentageAvailable": 19,
      "thresholdPercent": 20,
      "amount": 25
    }
  }
}

The event-specific payload is inside data.data. schemaVersion identifies its version; ignore unknown optional fields.

Allowance events include the company identifier, action and allowance details such as target, limit, dates, status and version. Company-capacity events include usage and availability. Bulk completion includes the job identifier and success/failure totals; retrieve the job to inspect individual errors.

Handle delivery safely

Follow the shared signature verification and delivery guide. Verify the signature using the raw request body, store the event durably, and acknowledge with 2xx before doing slow work.

Deduplicate using eventId, also sent in X-Webhook-ID. Repeated delivery must not repeat a customer notification or change your recorded balance twice. Events can arrive out of order; compare timestamps and allowance versions before replacing newer state.

Reconcile missed events

Use transaction reads or a credit export to reconcile activity in the confirmed environment. There is no partner-facing event replay API. A webhook delivery issue does not justify applying a new allowance change to recreate an event.

Next, use the credit API preview to read the relevant company or bulk job.