A key per use, and an event that reaches you the moment it happens
The key is shown once when created and never shown again — what we keep is its fingerprint, not the key. So whoever loses a key creates another and revokes the old one, and nobody — neither we nor you — can
API keys
| Name | Key | Permission | Last used | Case | Action |
|---|---|---|---|---|---|
| Company website | nq_live_7f2a•••• | Read only | 8 min ago | Active | |
| Accounting system | nq_live_c481•••• | Read and write | Yesterday | Active | |
| Developer sandbox | nq_test_19be•••• | Read only | 3 weeks ago | Idle |
Revocation is immediate and irreversible
3 keys · 1 Idle
The webhook
Your URL that we call on every eventAvailable events
6 events| Event | When it fires |
|---|---|
| customer.qualified | The lead passed the qualifying questions and became serious |
| quote.sent | A quote was issued and reached the customer |
| contract.approved | You approved the contract — not the system |
| payment.link_sent | The payment link was sent on WhatsApp |
| payment.received | The instalment was confirmed by the gateway after re-verification |
| conversation.escalated | A conversation was escalated to you |
Failed delivery attempts
Last 7 daysNo failed attempt
Every event in the last seven days was delivered on the first attempt. And had one failed, it would appear here with its full payload and a resend button — because a lost event with no trace is worse than