FOR DEVELOPERS. ON YOUR DEVICES.
From API
to Pliing.
Deploy complete. Backup saved. A job failed. Send an API call and get notified on the Apple devices you choose.
PRIVATE BETA API first. iPhone and Mac as receivers.
curl https://api.pliing.app/v1/notifications \
-H "Authorization: Bearer $PLIING_TOKEN" \
-H "Idempotency-Key: deploy-prod-1842" \
-H "Content-Type: application/json" \
-d '{
"to": "pliing-7m3k9-xr2n8-q4v6",
"title": "Deploy complete",
"body": "main → production. Everything is running.",
"level": "info"
}'
main → production. Everything is running.
Preview of the product flow. No notifications are sent here.
Idempotency-Key is a unique ID for the send. Reusing the same ID when retrying prevents duplicate notifications. The playground creates it automatically.
ONE ACCOUNT. ONE RECIPIENT ID.
Apple handles sign-in.
Pliing handles delivery.
Connect your code to your devices. Your account follows you; you control the receiving devices.
- 01
Sign in with Apple
The same account on iPhone, iPad and Mac. No need to create and remember another password.
- 02
Get your PliingID
A unique ID such as
pliing-7m3k9-xr2n8-q4v6tells the API which account should receive the notification. - 03
Connect your project
Create a scoped API key. Approve the sender, select devices and send your first request.
Your PliingID is the address. The API key provides access. A public ID alone never grants permission to send.
RIGHT MESSAGE. RIGHT PLACE.
The phone in your pocket.
The Mac on your desk.
You choose.
Devices are registered to your account. Turn push on or off for each device. Disabled or removed devices do not receive new notifications.
Your inbox follows your account, even when push is disabled on a device.
Try the switches. This illustrates device selection and does not change any account.
A SMALL API. A CLEAR CONTRACT.
Fits into the tools
you already use.
One HTTPS call with JSON. Scoped keys, consent and duplicate protection are part of the contract from the start.
Read the API documentation ↗/v1/notificationsSend a notification/v1/consent-requestsRequest permission/v1/inboxSync the inbox202 Accepted means accepted by the API.Apple accepting a push and the user reading a notification are separate states. Each has its own meaning.
CONTROL ALL THE WAY
Every ping should be welcome.
You approve the sender
A project needs permission before sending. You can revoke it at any time.
403 consent_requiredKeys can be scoped and revoked
One key per project or integration. A sender key does not grant access to the recipient's inbox.
A retry should not create another notification
Use the same idempotency key when retrying. The API recognizes the event.
Idempotency-KeyFIRST MILESTONE
One call. One recipient.
A real Pliing.
The private beta has Apple sign-in, API keys and device preferences. Real API-to-push delivery has been tested with Apple's sandbox; the public App Store release will follow.
GOOD TO KNOW
A few quick answers.
Do I use my Apple ID as the recipient ID?
No. Sign in with Apple is used for authentication. Pliing creates its own stable, unique account ID. You send to that ID without sharing an email address or Apple's internal user identifier.
Can anyone who knows my PliingID send me push?
No. The sender needs a valid API key and your account's permission. You also decide which registered devices receive push.
Do all devices receive the same notification?
Your account has one shared inbox and separate push preferences for each device. For example, enable push on iPhone and Mac and disable it on iPad.
How do I use my ID with other services?
Copy your entire PliingID from the app and paste it into notification settings in a service that supports Pliing. The service requests permission with its own API key. Approve the request under Senders in Pliing before notifications can be sent. For your own scripts, create a project and API key in the API tab.
What about monitors, one-time codes and subscriptions?
We are completing the core: accounts, API keys, recipient IDs, devices and reliable push. One-time codes have a separate API under testing. Monitors and billing have not launched publicly.