Send what happens in your line to your other tools
Webhooks tell your other tools the moment someone joins, is called or books. API keys let your own reports and dashboards read your data. Both are on the paid plans.
- Signed webhooks
- Zapier, Make or your own system
- Delivery history
- API keys, shown once
Webhooks: events, as they happen
Open Integrations in the dashboard, click Add a webhook, and NextUp sends a web request to the address you choose each time one of your chosen events happens.
- Line events.Someone joins, is called, a visit starts or finishes, someone called does not show up, someone leaves, or a location starts or stops taking walk-ins.
- Appointment events.An appointment is booked, canceled or moved, and someone with one arrives or does not come.
- Zapier, Make or your own.Paste a Zapier or Make webhook address, or any web address that accepts a POST.
- Out only.It sends events out. It never reads from your system.
Add a webhook: a label, a web address and the events to send.
Signed, tested and traceable
You can check each request is genuine, try it before you rely on it, and see what happened to every delivery.
- Signed.Each request carries an HMAC signature in the NextUp-Signature header, so your server can check it came from us. You can rotate the secret.
- Test sends.Send a test event to see it arrive before real ones do.
- Delivery history.Every send is listed with its response code. If one failed you can see the error and retry it.
API keys: your data, your tools
For a custom dashboard, automated reporting or something webhooks alone cannot do, create a key under API Keys in the dashboard.
- Shown once.Copy the key when you create it. The full key is displayed only then, so keep it in a password manager.
- A Bearer token.Send it in the Authorization header of each request.
- Treat it like a password.A key has an owner’s permissions. Keep it on your server and never put it in website code.
- Revoke in one click.Delete a key and anything using it stops at once. Make and switch to a new one first.
Create key: give it a name that says what it is for.
How it works
- 1
Pick the events
Decide what your other tool needs to hear about.
- 2
Add the address
Under Integrations, add a webhook with a label and the web address.
- 3
Send a test
Check it arrives and that your side accepts the signature.
- 4
Watch the history
Every delivery is listed with its response code.
Who it’s for
Barbershop
Post to a staff chat when someone joins, so the owner away from the shop knows the line is moving.
Restaurant
Log every finished visit to a spreadsheet for your own end-of-week numbers.
Vet clinic
Send arrivals and missed appointments to the system your front desk already uses.
The small things
Out only
Webhooks send events out. They never read from or change your other system.
Keys you control
Name each key for what it does, so you know which to delete.
Setup steps
The help centre has the steps for webhooks and API keys.
Questions
Which plans have it?
Webhooks and API keys are on the paid plans. They are not on the Free plan.
Do I need Zapier or Make?
No. They are two easy destinations. Any web address that accepts a POST works.
Can an API key damage my account?
A key has an owner’s permissions, so keep it private and on your server. Delete it and it stops working at once.
Does NextUp connect to other point-of-sale systems?
Not directly. Webhooks and the API are how your own tools can connect.
Goes well with
Connect your line to the rest of your tools
Start the free trial, add a webhook and send a test event.