Platform overview
ResQueServe consists of two services. Both have a REST API, and both accept the same access tokens.
| Service | Purpose |
|---|---|
| Dashboard | Accounts, dispatch centers and their data (units, POIs, keywords, radio groups, address lookups). It is also the authorization server: all tokens are issued here. |
| Realm | The running sessions. It is a resource server: it validates the tokens issued by the Dashboard and issues none itself. |
Note
For the SIM Dispatcher, the services run at these hosts:
| Environment | Dashboard | Realm |
|---|---|---|
| Production | www.sim-dispatcher.com |
platform.sim-dispatcher.com |
| Stage | stage.sim-dispatcher.com |
stage-platform.sim-dispatcher.com |
Where to start
- Call the API from your own code? Create an API client in your account and use the .NET SDK, or request tokens yourself as described in Authentication.
- Build an application that acts on behalf of a user? Use the authorization code flow with PKCE.
- Look up types and models? See the API reference (
XENBIT.ResQueServe.AbstractionsandXENBIT.ResQueServe.Core).
Every Dashboard and Realm instance publishes the interactive OpenAPI documentation of its endpoints at /api-docs.