WebToAppMaker

Push Notifications

Push Notification API

Trigger a push send from a trusted server through the current authenticated dashboard API.

Before you start

  • Configured Firebase module
  • A valid WebToAppMaker bearer token belonging to an app owner or collaborator
  • Server-side code that can protect the token

Configure and verify

  1. Authenticate server-side

    Send Authorization: Bearer YOUR_TOKEN. Never expose this dashboard token in public website JavaScript.

  2. Choose the endpoint

    POST JSON to /api/apps/{app_id}/push/send on the configured API host.

  3. Build the payload

    Provide audience, title or body, and optional recipient_identity, direct_token, open_url, image_url, and data_json.

  4. Handle the accepted response

    HTTP 202 means processing was accepted. Inspect status, attempted, sent, failed, and results.

  5. Plan credential isolation

    For production automation, use a dedicated integration account or add scoped service tokens before allowing broad third-party access.

Example request

curl -X POST "https://api.webtoappmaker.com/api/apps/APP_ID/push/send" \
  -H "Authorization: Bearer DASHBOARD_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"audience":"selected_identity","recipient_identity":"customer-123","title":"Order update","body":"Your order is ready","open_url":"https://example.com/orders/123"}'

Current authentication scope

Test before release

  • Call originates on a trusted server
  • Token is never sent to browsers
  • Failures are logged without full FCM tokens
  • Audience is validated before send