Webhooks

Webhooks

Partner applications can subscribe to workspace events (customers, vendors, transactions, invoices, bills). COUNT delivers JSON outbound HTTP POST requests to your HTTPS callback URL when a subscribed event occurs.

Subscriptions are scoped to the authorized workspace (from the partner access token). Deliveries are processed asynchronously (queue + worker). Only subscriptions with status: active receive deliveries.

---

Authentication

All webhook subscription endpoints require:

• HMAC authentication — x-client-id, x-signature, x-timestamp (see Getting Started / API Access Credentials for the signing algorithm).

• Partner access token — Authorization: Bearer <access_token> from the OAuth / token exchange flow.

Use Content-Type: application/json on POST and PATCH so the request body matches your HMAC body hash.

---

Event names (v1)

Dot-notation event strings:

• Customer: customer.created, customer.updated, customer.deleted

• Vendor: vendor.created, vendor.updated, vendor.deleted

• Transaction: transaction.created, transaction.updated, transaction.deleted

• Invoice: invoice.created, invoice.updated, invoice.deleted

• Bill: bill.created, bill.updated, bill.deleted

Customer and vendor soft-deletes (isDeleted false → true) emit .deleted, not .updated.

Transaction, invoice, and bill use different hook logic: soft-delete is often an update, so you may receive .updated until a hard destroy triggers .deleted. See When events fire for the full matrix.

---

Base path

All subscription management routes share the base path:

/partners/webhooks

---

Reference

• When events fire — detailed triggers for customer, vendor, transaction, invoice, and bill (create / update / delete and soft vs hard delete).

Available endpoints

• List Webhook Subscriptions — GET /partners/webhooks

• Create Webhook Subscription — POST /partners/webhooks

• Update Webhook Subscription — PATCH /partners/webhooks/{uuid}

• Delete Webhook Subscription — DELETE /partners/webhooks/{uuid}

For what COUNT sends to your server, see Outbound Deliveries.