Skip to main content
Argus is the operations platform for the UK London Mayfair ER:LC community. It covers dispatch (CAD), officer terminals (MDT), civilian characters and police records (PNC), staff and moderation, and live data from the game server. This site documents the HTTP API behind the Argus web application, as it is implemented today.
This is an internal application API. It exists to serve the Argus web application and the community’s own integrations. It is not a stable public API: there is no versioning, paths and fields can change with any release, and browser requests only work from the application’s own origin. Build against it only if you are part of the project.

​
What is here

Authentication

Discord sign-in, the session cookie, service credentials and Developer Access.

Quickstart

Make a first authenticated request and read the response envelope.

Permissions

Every permission key, what it allows, and which endpoints check it.

Errors

The error envelope, status codes and what a 409 means.
The API reference tab is generated from an OpenAPI 3.1 document, api-reference/openapi.json, kept next to these pages. It lists all 86 implemented operations with their permissions, parameters, request and response shapes, examples and errors.

​
API areas

​
Conventions at a glance

  • Every path is under /api on the deployment’s own origin.
  • Requests and responses are JSON. Timestamps are UTC, ISO-8601.
  • Success responses are wrapped as { "data": ... }, with meta on lists. Failures are { "error": { "code", "message" }, "requestId" }.
  • Permissions are checked on the server for every request. What the web application shows or hides is never the boundary.
See API conventions for the detail, and API status for what is and is not implemented.