Push notification API documentationOne request, one sound.

One POST puts a notification on your phone. The same API repeats emergencies, escalates them, cuts the noise, watches your jobs and tells you which device got what.

Base URL: https://acciti.com/v1
Auth: Authorization: Bearer
Body: application/json
Success: 202 Accepted

Your first notification

curl https://acciti.com/v1/messages \  -H "Authorization: Bearer $ACCITI_TOKEN" \  -H "Content-Type: application/json" \  -d '{ "user": "your-user-key", "message": "Payment received" }'

Quickstart

About three minutes, start to sound.

1
Sign in and install the app
Sign in with a passkey, then install Acciti on your iPhone or Mac and sign in there too. That registers the device that will ring.
2
Copy your user key
It's on the dashboard and in the app. A user key can only send to you and can't read anything, so it's safe in a script.
3
Create a sender
Make one per script or service. Each gets a sender token that can send and do nothing else. Revoke a leaked one and the others keep working.

Send

Put your token and user key into this request and run it.

Terminal

curl https://acciti.com/v1/messages \  -H "Authorization: Bearer $ACCITI_TOKEN" \  -H "Content-Type: application/json" \  -d '{ "user": "your-user-key", "message": "Payment received" }'

Two seconds later

A 202 came back and nothing rang?

Look at deviceCount in the response. 0 means no device is signed in to your account yet. Sign in on the app and send again.

The full reference

Get started

Credentials
Three credentials, each able to do no more than its job needs.
Send a message
One POST to /v1/messages, in curl, Python, JavaScript, Swift or Go.

Alerting

Priorities and quiet hours
From silent to an emergency, and what still rings during quiet hours.
Emergencies
An emergency keeps ringing until someone acknowledges it.
Resolve an alert
When the service recovers on its own, close the alert from your code.
Escalate to whoever is on call
An unacknowledged alert moves on to whoever is on call next.

Noise control

Make retries safe
A webhook delivered twice sends one notification.
Collapse repeated alerts
A flapping service rings once, not every time it flaps.

Monitoring

Monitor scheduled jobs
One curl at the end of the job, and a missed run rings your phone.
Receive events from other services
Point a service's webhook at a connector, and its events reach your phone.

Delivery

Sounds
A different sound for a sale and an outage, so you know which from across the room.
Delivery receipts
Which device got the notification, and why one didn't.
Outbound webhooks
Hear back when someone acknowledges, in a signed request to your server.

Reference

Errors
One error shape, a code that never changes, and what to do about each.
Plans and limits
What a plan limit looks like to your code, and what happens past it.