Developer Tools
The Developers page is the console-side home for API access: create and revoke API keys, register webhook endpoints, watch deliveries, and retry failures — all without leaving the product. Public API reference documentation lives here on the website under Developer Center.
Open it at Configuration → Developers.
When should I read this?
- Your integration needs a key and you are not sure how to issue one safely.
- A webhook stopped arriving and you need delivery evidence.
- You changed webhook URL and want to re-point the endpoint.
Use cases
| Scenario | What you do |
|---|---|
| New integration going to production | Create a key named for the environment, store it in the secret manager immediately. |
| "Did the invoice.paid webhook fire?" | Open History on the endpoint: every event, its status, and attempt count. |
| Your downstream service was down for an hour | Find the failed deliveries and hit Retry — no replay scripting needed. |
API keys
Create a key
Click Create key
Give it a name that says where it runs ("Production Server", "CI pipeline") and, optionally, an expiration date.
Copy the secret — once
The full secret is shown exactly once with a copy button. When you close the dialog it is gone forever; only a masked prefix remains in the list.
Store it properly
Keep it in your secret manager before closing the dialog. Anyone with the key can act as your organization against the public API.
Manage keys
The list shows each key's masked prefix, status (Active / Revoked), creation date, and last-used time — a quick way to spot keys that should have been retired. Revoking is immediate and cannot be undone; there is no in-place rotation, so the safe rotation pattern is create new → deploy → revoke old.
Webhooks
Register an endpoint
Click Add endpoint, enter the HTTPS URL, and select at least one event:
| Event | Fires when |
|---|---|
invoice.paid |
An invoice is settled. |
invoice.posted |
An invoice is finalized (bill run, conversion, amendment). |
invoice.payment_failed |
A charge attempt failed. |
subscription.created |
A subscription comes into existence (e.g. from a subscription order). |
subscription.canceled |
A subscription ends. |
subscription.activated |
A subscription starts billing. |
Creating the endpoint shows the signing secret once — store it to verify payload signatures (see webhook signature verification).
Monitor and operate
Each endpoint row shows its events, Active/Inactive toggle, and History: the delivery record per event with attempt counts and status. A failed delivery can be retried from history with one click. Endpoints can be paused (toggle), re-pointed (edit URL), or deleted.
How the pieces fit
A typical integration loop: your backend holds an API key for reads/writes, listens on webhook endpoints for state changes, and uses delivery history as the reconciliation evidence when something looks missed. Idempotency and signature verification rules are covered in the API reference.
Common issues
- The key is lost. It cannot be recovered — revoke it and create a new one.
- Webhooks arrive unsigned/verification fails. You rotated the endpoint but kept the old signing secret; re-copy the secret from the endpoint settings.
- Missed events during downtime. Filter history to the outage window and retry the failures; delivery history is your replay source.