Send a user access token with every business request.
The token selects one user and one organization. Arcane also checks the permission shown below and any applicable Application, external-auditor, or Case access boundary.

User context

Applications

An Application is the product or compliance boundary used by the current Compliance Platform implementation. These methods use the Application’s numeric ID. Application-scoped Case and report methods use its foreignId route segment instead.

Asset catalog, contracts, and audits

These User API resources support the current Compliance Platform interface. They are separate from the Service API’s confidential Asset resource.

Organisation and team management

Case requests and Cases

Use foreignId to select the Application. Creating a Case creates a pending request. Approval creates the Case when the approval requirement is satisfied.

Reports

Report downloads return CSV content. Listing and downloading use separate permissions.

Activity log

Service API key administration

These are User API methods. They create and revoke credentials that your backend then uses with the Service API.

Arcane platform sign-in routes

The Arcane interface uses the following WorkOS-backed routes. External applications should use the OAuth contract in Authentication instead of coupling to these interface-specific flows.