Browse docs +

FAQ

When something goes wrong, keep the request time, the HTTP status, and the request_id. Hide your key before sharing screenshots or logs.

The request succeeded, but no notification appeared#

A 200 response means Apple or Google accepted the notification, not that the phone displayed it. Check in this order:

  1. The link in the app matches the one in your script. Resetting the link replaces the key.
  2. Notifications are allowed for Breeze in system settings.
  3. A Focus or Do Not Disturb isn't hiding it. Try level=timeSensitive, or check Breeze's Focus filter.
  4. The group isn't muted in Settings → Muted groups.
  5. On Android, the Breeze notification channel for that level is turned on, and battery optimization isn't blocking the app.

If the notification shows up in History but not as a banner, the problem is a system setting rather than delivery.

I get 404#

The key is unknown or no longer active. This happens after you reset the link, reinstall the app, or copy only part of the link. Copy the current link from the app and update your script.

I get 422#

A parameter isn't supported on the target device. Common causes: critical (not available yet), and on Android badge, ciphertext, custom sounds, or sound=none. The response's error names the problem. Remove the parameter, or see Parameters for the platform column.

I get 429#

You sent too many requests in a short time. Wait for the number of seconds in Retry-After before trying again. Limits are per key and per public IP, so devices behind the same office or home network share one allowance. See the API reference for current limits.

I received the same notification twice#

A timeout or a dropped connection can happen after Apple or Google already accepted the notification, so retrying shows it again. Don't retry automatically after a timeout, and never resend a whole group after a 207. Giving messages an id lets a retry replace the first copy instead of adding a second.

Images or sounds don't load#

Images, icons, and remote sounds must use HTTPS and download within 10 seconds. Remote sounds must be .caf files of up to 6 MB. Custom sound names must match the name shown in Settings → Sounds.

Reset the link in the app. The old key stops working on the next request. Then update every script and tool that used the old link. A key can only send, so nobody could read your history with it.

Can I use my existing Bark scripts?#

Mostly yes. Replace the host and key with your Breeze link. The path forms, /push with device_key, and Bark's parameter names all work.

Can I run my own server?#

No. Breeze runs as one hosted service at push.breezelabs.dev, so the app works without setup. Encryption keeps your content private from the service.

Does Breeze work on Android?#

Yes. Android uses the same links and most parameters. Encryption, custom sounds, badges, and critical alerts are iPhone only for now.

Are critical alerts available?#

Not yet. They need an entitlement from Apple. Until then, use level=timeSensitive with call=1. See Sounds and alert levels.

Is the service up?#

The service status page checks the service and its connections to Apple and Google.