PUSH API · v1a
Core concepts
Even for the same app, different environments have separate keys, devices, push service connections and message targets. Check the active scope before acting.
| Concept | Meaning |
|---|---|
| Organization | Groups the accounts and projects operated together. |
| Project | Groups related apps. Project environments separate shared user data and definitions. |
| App | A client application, such as an Android or iOS app. |
| App environment | The scope for keys, push service connections, installations and messages. A key is pinned to one app environment. |
| App user | A user identity. Enrollment creates an anonymous user. Managed login uses device authentication plus an external ID in BASIC, or a JWT from your trusted backend in VERIFIED. BASIC does not verify ownership of the ID. |
| App installation | One installation of an app on a device. A user may have several installations. |
| Push subscription and address | A push delivery route for an installation. Forward new FCM/APNs addresses to the SDK when they change. |
| Message and delivery | A message is the send request; a delivery is the processing outcome for one subscription. |
Three different settings
- OS notification permission: whether the operating system allows notifications.
- App push preference: whether the user opted into push inside the app.
- Marketing consent: a separate record for marketing messages. OS permission and push preference do not replace it.