HOW IT WORKS
One API, multiple providers
Your application describes its intended notification. The platform translates it to web push, FCM or APNs using project-level credentials and provider-specific validation.
Safe retry behavior
Idempotency keys prevent accidental double creation when clients retry requests. Rate limits and tenant quotas protect the shared infrastructure.
Webhooks and event history
A versioned delivery event schema would enable downstream analytics and operations. Webhook signatures, replay protection and retry policies are required before public launch.
Documentation that can be tested
OpenAPI 3.1 schema, executable examples, a sandbox environment and error references are planned before we describe the API as publicly available.
Example request (planned)
This is an illustrative contract to explain the design. The API does not yet accept requests.
POST /v1/notifications
Idempotency-Key: appointment-452
{
"project_id": "proj_demo",
"user_id": "customer_128",
"title": "Appointment reminder",
"body": "Your appointment is tomorrow",
"schedule_at": "2026-11-15T14:00:00-03:00",
"expires_at": "2026-11-15T15:00:00-03:00"
}The service is in development. Any API shown is a proposed interface, not an active endpoint.