Environment and URLs
Staging
| Service | URL |
|---|---|
| Product | https://beta.notify.callistech.co.id |
| API | https://beta.api.notify.callistech.co.id |
| Console | https://beta.notify.callistech.co.id/console |
| Documentation | https://beta.docs.notify.callistech.co.id |
| Swagger API Reference | https://beta.docs.notify.callistech.co.id/api-reference/ |
Production
| Service | URL |
|---|---|
| Product | https://notify.callistech.co.id |
| API | https://api.notify.callistech.co.id |
| Console | https://notify.callistech.co.id/console |
| Documentation | https://docs.notify.callistech.co.id |
| Swagger API Reference | https://docs.notify.callistech.co.id/api-reference/ |
These are the environment addresses. Feature availability depends on the version deployed to that environment.
Swagger derives the API origin from the documentation hostname: beta.docs uses beta.api, and docs uses api. The documentation build uses DOCS_URL for its canonical site URL.
Local development
The API defaults to http://127.0.0.1:8080. A Docusaurus development server can run separately with npm start inside website/. When using the combined Docker image directly, its static documentation mount is /__docs/; the public documentation proxy normally hides this prefix.
Keep environments separate
Use separate applications, keys, accounts, providers, and test recipients for staging and production. A key is bound to its registered application; changing a URL does not turn a staging key into a production key. Set the API base URL and secret through your backend configuration.