Sapagan developer docs
Sapagan sends push, email and in-app messages for companies in Indonesia. These docs are for the developers who connect an app or a backend to it.
Start with the quick start. It takes you from a key to a first push in about 15 minutes.
Where to go#
| If you want to | Read |
|---|---|
| Send a first push | Quick start |
| Understand the model | Organisations and workspaces, Profiles and identifiers |
| Pick the right key | API keys |
| Protect device registration | Identity tokens |
| Add push to an app | Flutter or Web |
| Call the API from your server | Server SDK and the API reference |
| Send a chat or order message now | Transactional messages |
| Move from Customer.io | Migrating from Customer.io |
The pieces#
- The API lives under
/v1. You call it with a key from your backend, or with an app key from an app or a web page. - The SDKs register devices and report opens:
sapagan_flutterfor Flutter,@sapagan/webfor browsers. - The console is where your team writes campaigns, builds journeys, reviews messages and manages keys.
- Compatibility routes (
/api/v1and/api/v2) accept the Customer.io Track API, so a backend can switch by changing its base URL and credentials.