Overview
Notify is the shared notification service from CALLISTECH INDONESIA (PT Callis Tech Indonesia). Your application submits a business event through one API; Notify handles message rendering, channel delivery, inbox storage, retries, and delivery status.
What you can build
- Transactional email, WhatsApp, and Discord notifications.
- An in-app notification inbox with unread counts and read actions.
- Live inbox updates using Server-Sent Events (SSE).
- Browser notifications using standards-based Web Push.
- Separate notification configuration for each customer organization.
Start here
- Read Concepts and glossary to understand the data boundaries.
- Read Architecture to see the delivery and browser flows.
- Follow the Quickstart to send an in-app notification.
- Follow Implementation guide to connect your application.
- Use Scopes and permissions when creating credentials.
Responsibility boundary
Your application owns user login, business rules, customer membership, and authorization. Notify does not know whether a signed-in user may access an organization in your application. Your backend must make that decision before selecting an account, sending a notification, or issuing a user token.
Notify owns notification data and verifies the credentials, application boundary, account identifiers, and endpoint permissions it receives.
| Interface | Who uses it | Purpose |
|---|---|---|
| Notify Console | Platform operators and tenant teams | Configure tenants, applications, accounts, credentials, providers, templates, and routes |
Application API, /v1/* | Your backend | Send notifications, synchronize accounts, and issue user tokens |
User API, /v1/user/* | Your frontend with a user token | Read one user's inbox, subscribe to live updates, and manage push |
Admin API, /admin/v1/* | Authorized platform automation | Provision tenants, applications, and application credentials |
| API Reference | Developers | Inspect request schemas and try endpoints |