Notification API
Send email, SMS, webhook and in-app notifications, configure templates and recipients, and read delivery status.
- Service
- Notification service
- Base path
https://your-notification-host/api- Authentication
- Bearer token, or the service key for internal callers.
Most notifications are configured and fired by triggers, approvals and workflows. These endpoints send directly or run a configured notification. Routes include a workspace key that identifies the app context.
/api/notification/workspace/{workspaceKey}/send/{notificationId}Send a configured notification
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/notification/workspace/{workspaceKey}/emailSend an email
Delivered through the tenant's configured email provider (SMTP or Brevo).
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/notification/workspace/{workspaceKey}/smsSend an SMS
Delivered through Twilio.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/notification/workspace/{workspaceKey}/in-appSend an in-app notification
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/notification/workspace/{workspaceKey}/webhookCall a webhook
Supports Basic and Bearer authentication, with retries.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/notification/workspace/{workspaceKey}/multi-channelSend on several channels at once
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/notification/workspace/{workspaceKey}/pushComing soonSend a push notification
The route exists, but a push provider is not yet available for delivery.
/api/notification/config/upsertCreate or update a notification configuration
Templates use Liquid and can include data from saved queries. Recipients can be addresses, the record owner, a role or a query.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/status/workspace/{workspaceKey}/{notificationId}Get a notification's delivery status
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/status/workspace/{workspaceKey}/history/{recipientId}Get a recipient's notification history
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/wsIn-app notification socket
Clients read notifications, mark them read and clear them over this WebSocket. The access token is sent on the handshake.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/records/insertStore a user's channel preferences (a platform entity)
Per-user opt-in and opt-out per channel is stored as a platform record and applied when notifications are sent.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.