Send With HTTP

Use HTTP when your sender can make authenticated HTTPS requests but cannot run the BeeBuzz CLI.

HTTP sends use trusted delivery. BeeBuzz receives the notification content so it can deliver it to your devices.

Authentication

Create an API token in the BeeBuzz web app.

Send it as a bearer token:

Authorization: Bearer $TOKEN

Send A Notification

curl https://push.beebuzz.app \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Build finished",
    "body": "main passed CI",
    "priority": "normal"
  }'

Send To A Topic

Use the topic in the path:

curl https://push.beebuzz.app/alerts \
  -H "Authorization: Bearer $TOKEN" \
  -F title="CPU high" \
  -F body="The server is above 90%"

Topic names use lowercase letters, numbers, and underscores. They must start with a letter.

Priority

Supported priorities:

• normal
• high

If you omit priority, BeeBuzz uses the default behavior for the send path.

Attachments

For a remote HTTPS attachment, send JSON with attachment_url:

curl https://push.beebuzz.app/alerts \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Report ready",
    "attachment_url": "https://example.com/report.png"
  }'

For an uploaded file, use multipart form data:

curl https://push.beebuzz.app/alerts \
  -H "Authorization: Bearer $TOKEN" \
  -F title="Snapshot" \
  -F attachment=@snapshot.jpg

In trusted delivery, BeeBuzz receives attachment content before preparing delivery.

Current limits:

• title: 64 characters
• body: 256 characters
• attachment content: 1 MiB
• multipart request body: 1.5 MiB

Responses

A successful request returns delivery counts:

{
  "status": "delivered",
  "sent_count": 1,
  "total_count": 1,
  "failed_count": 0
}

See the API Reference for exact request and response fields.

Common Issues

If the request succeeds but no notification arrives:

• confirm the device is paired
• confirm the device is subscribed to the topic
• confirm the API token can send to the topic
• check notification permission on the receiving device