Carillon docsFAQ
Find answers about setup, delivery, device behavior, and billing.
| Question | Answer |
|---|---|
| How do I send my first notification? | Follow the quickstart. |
| Which key belongs in the mobile app? | Use a mobile key. See authentication. |
| Can I rotate a mobile key without breaking old versions? | Keep the old key active while those versions are supported. See rotation. |
| Does registration show a permission prompt? | No. Call requestPermission() separately. See devices. |
Does sent mean the user saw the notification? | It means APNs or FCM accepted it. See delivery statuses. |
| How do I retry a send without duplicating it? | Reuse its Idempotency-Key and identical request body. See retries and deduplication. |
| What happens after an uninstall? | Provider feedback invalidates the token. See token lifecycle. |
| Can one person have several devices? | Yes. Devices can share an external_id. See user identifiers. |
Why is opened_at null? | No open was recorded. Check the callback setup in track opens. |
| How do I separate staging from production? | Create a separate Carillon app. See environment isolation. |
| Where is data stored and sent? | See data residency. |
| Which devices count for billing? | See the Monthly Reachable Devices definition. |
| How do I get an account? | Create an account with your email and password; a workspace is created for you. To join an existing organization, ask its admin for an invitation. |
For an integration failure, start with troubleshooting or look up the API error code.