Push Notification API

Push notifications from cURL.
Your script ends, your phone buzzes.

Send a push notification to your iPhone or Android phone with a single cURL call. Paste it at the end of a deploy, a backup, a CI job or a long training run, and the alert reaches you wherever you are.

No app to publish, no Firebase project, no APNs certificate. Create an inbox in AgentsRoom, copy its endpoint and its send-only key, and every notification also stays in a searchable history on your desktop and your phone.

deploy.sh

$ curl POST /api/dev-inboxes/…/push

{"title":"Deploy finished"}

202 Accepted

Your phonenow

Deploy finished

api v2.4 is live in production

One HTTPS request from any script, one notification on your phone, a copy kept in the inbox.

Most long tasks end in silence. The deploy finished twenty minutes ago, the nightly backup failed at 3 a.m., the migration is still waiting for you, and you only find out when you go and look. A push notification is the cheapest way to stop looking, but wiring one up usually means a mobile app, a Firebase project and certificates to renew.

AgentsRoom already lives on your phone. The Push API turns it into the receiver: each inbox gets its own HTTPS endpoint and a send-only key, and anything that can run cURL can now reach your lock screen. A shell script, a GitHub Actions step, a cron job, a server event in your own app.

Every alert is also stored on the server, in an inbox you can search from your desktop or your phone. Your computer can be closed: the endpoint, the inbox and the delivery all run on AgentsRoom's servers.

Everything a notification needs, nothing to host

One JSON body, one header for the key, and a few guarantees that matter once a script runs unattended.

Title, body, link and image

Send a title of up to 160 characters, a body of up to 16,000, a link to open and a public HTTPS image. The phone shows a short preview, the inbox keeps the full text.

Sound or silent

Each inbox has a default sound, and every request can override it: the device sound for a failed backup, silent for a routine report.

No duplicates when a script retries

Add an Idempotency-Key header and a retried request returns the same message instead of buzzing your phone twice. It does not count against your allowance again.

Send-only keys you can revoke

The key in your script can only send. It cannot read the inbox or change its settings. Regenerate it if it leaks, or revoke it to stop new messages at once.

Works with your computer off

The endpoint and the inbox run on the server. Sign in to the AgentsRoom mobile app with the same account, allow notifications, and close your laptop.

Private, or shared on purpose

An inbox belongs to your account or to one project. In a Team or a Pro group, choose the teammates who also receive its alerts. They never see the key.

The whole integration is one request

Copy it from the inbox settings, with your real endpoint and key already filled in.

A deploy alert from a shell scriptPOST /push
curl -X POST https://agentsroom.dev/api/dev-inboxes/INBOX_ID/push \
  -H 'Authorization: Bearer SENDING_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: deploy-2481' \
  -d '{"title":"Deploy finished","body":"api v2.4 is live","sound":"default",
       "linkUrl":"https://example.com/releases/2481"}'

A 202 response means the message is stored in your inbox. Delivery to the phone then depends on the operating system, your notification settings and the push service. On Windows, the copy button gives you a PowerShell version that calls curl.exe.

From zero to your first notification

Three steps, about two minutes, no account on another service.

01

Open Push and create an inbox

In a project, click Push in the project dock, or open it from the notification settings. Pick your account or the current project, and start from a template such as New installation or Deployment finished.

02

Copy the cURL command

Connection & settings shows the endpoint, the send-only key and a ready-to-run request. Edit the title and body, then save the integration so the same template follows you on every machine.

03

Run it from your script

Paste the command at the end of your deploy script, your CI job or your cron task. The next run sends the notification, and the message appears in the Push tab on desktop and mobile.

What developers wire up first

Anything that ends while you are not watching is a good candidate.

Deploy finished or failed

Add one line at the end of the deploy script or the CI job, with a link to the release or to the failing logs.

A new user or a new install

Call the endpoint from your backend when someone signs up, installs your app or upgrades, and celebrate from your phone.

Backups and cron jobs

Use the device sound when a nightly backup fails and stay silent when it succeeds. The history shows which nights went wrong.

Long builds, imports and training runs

Stop checking a terminal every ten minutes. The job tells you when it is done, even if you left the desk.

Built to live inside your scripts

The key travels in an Authorization header, never in the URL, so it does not end up in proxy logs. It is 192 bits long, stored hashed for lookup, and shown only to the owner of the inbox.

A key that leaks is cut off in one click: regenerate it and the old one is refused from the next request, or revoke it to stop the inbox from accepting anything. Messages already received stay readable.

Treat what arrives as untrusted content. Images are loaded from their public host when you open a message, and links only open when you tap them.

MCP

Ask your agent to wire it up

dev_inboxes_listdev_inbox_createdev_inbox_configuredev_inbox_membersdev_inbox_messagesdev_inbox_test

Say "notify me on my phone when someone installs my app" and your AI coding agent can create the inbox, configure the template and add the call to your code with the AgentsRoom MCP tools. Every agent gets them, whatever its CLI: Claude Code, Codex, Antigravity and the others.

The agent asks before it changes a setting or shares an inbox, and it never commits a sending key to your repository.

Discover AgentsRoom MCP

Monthly push allowance

Counted per calendar month, across all your inboxes. Email has its own separate allowance.

Guest

10

per month

Free

100

per month

Plus

200

per month

Pro

Unlimited

Team seats include Pro. Messages are kept for 90 days, and deleting one does not give back its notification.

Your services send emails rather than HTTP requests? Give them a dedicated address instead.

Developer email inbox

Want to know when an AI agent finishes its turn rather than when your script does? That is a separate, built-in notification.

Agent notifications

Push notification API: questions

How do I send a push notification to my phone from cURL?

Create a Push inbox in AgentsRoom, copy its endpoint and send-only key from Connection & settings, and run a POST request with a JSON body containing at least a title. Sign in to the AgentsRoom mobile app with the same account and allow notifications to receive it.

Does my computer need to stay on?

No. The endpoint, the inbox and the delivery run on AgentsRoom's servers. Your laptop can be closed: the notification still reaches your phone and the message waits in the inbox.

Does it work on both iPhone and Android?

Yes. Notifications go to every device signed in to your account in the AgentsRoom mobile app on iOS and Android. Tapping one opens the message in the right inbox.

What can a notification contain?

A title of up to 160 characters, a body of up to 16,000, an optional public HTTPS image, an optional HTTPS link and the sound: the device default or silent. Custom sound files are not supported.

How do I avoid duplicate notifications when my script retries?

Send an Idempotency-Key header with a value unique to the event, such as the deploy number. A retry with the same key returns the original message without a second notification and without using your allowance again.

What happens if my sending key leaks?

The key can only send messages, never read them. Regenerate it in the inbox settings and the old key is refused from the next request, or revoke it to stop new messages until you create a new one.

How many notifications can I send?

Per calendar month and across all your inboxes: 10 as a guest, 100 with a free account, 200 with Plus and unlimited with Pro. Team seats include Pro. Email has its own allowance.

Can my teammates receive the same alerts?

Yes, in a Team or a Pro group. The owner picks the teammates who can read the inbox and receive its notifications. They never see the sending key and cannot change the settings.

Related features

Let your scripts tap you on the shoulder

Download AgentsRoom, create a Push inbox and send your first notification in two minutes.

FreeDownload AgentsRoom

Companion app: monitor your agents on the go

Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.

Get the extension
Chrome Web Store

Push bugs and requests straight to your public backlog.

Multiple projects
Multi-provider
Multiple agents
Live status
File diff & commit
Mobile companion
Live preview
Agent teams
Browser automation
Backlog-driven dev
Prompt Library
Skills Library
View all features