API keys and webhooks

Connect your own tools and automations: read your contacts, inbox, bookings and orders, and get new ones as they happen. On the Business plan.

Open Settings → Developers. Only the owner or an admin can manage keys and webhooks.

API keys. Create a key, give it a name (what it's for) and choose Read only or Read and add contacts. Copy it straight away: it's shown once. Send it as `Authorization: Bearer np_…` to `https://api.nexopages.com/public/v1`: `/contacts`, `/inbox`, `/bookings` and `/orders` list the newest first (50 at a time, then follow `next`), and a write key can add a contact with `POST /contacts`. Each key can make 120 requests a minute. Revoke a key and it stops working at once. The full reference is at `api.nexopages.com/docs`.

Webhooks. Add an https address and choose what to send (leads, bookings, orders, sign-ups, reviews, messages, or everything). Each new inbox item is posted there as JSON within a minute, with the contact who sent it. Send a test checks it works; Recent sends shows what happened, and failed sends are retried for about 15 hours before you can send them again by hand. An address that only fails for 3 days is switched off.

Zapier and Make. Make a key with Read and add contacts, then use the NexoPages app in Zapier or Make: new leads, bookings, orders, sign-ups, reviews and messages arrive in your Zaps or scenarios within a minute, and you can add contacts. Until our apps are listed there, use their Webhooks trigger with the steps above.

Tip: To check a request really came from NexoPages, compute HMAC-SHA256 of `<t>.<body>` with your signing secret and compare it with `v1` in the `NexoPages-Signature` header.