System

API Applications

Issue narrow, revocable credentials for integrations without handing out database access.

Create API application

How to try the API

Create an application above, copy its one-time token, and send that entire client-id.secret value as a bearer token. Start with a read call before wiring up a full integration.

PowerShell

$token = 'paste-the-entire-token-here'
$headers = @{ Authorization = "Bearer $token" }
Invoke-RestMethod -Uri 'https://demo.cmiforge.com/api/v1/entities/clients' -Headers $headers

curl

curl "https://demo.cmiforge.com/api/v1/entities/clients" \
  -H "Authorization: Bearer paste-the-entire-token-here"

Quick diagnosis: 401 means the token is missing, malformed, rotated, or revoked. 403 means the application is valid but does not have the scope required by that endpoint. Tokens are tenant-specific and should be stored as secrets, never in source control.

Applications

Use Authorization: Bearer client-id.secret with the v1 endpoints.

No API applications yet.

Endpoint tester

Paste a one-time API token from an active application, enter test values, and call the real tenant API from this browser.

Stored only in this page while it is open.
List clients GET /api/v1/entities/clients
entities.read 
Not tested yet.
List matters GET /api/v1/entities/matters
entities.read 
Not tested yet.
List parties GET /api/v1/entities/parties
entities.read 
Not tested yet.
Create submission POST /api/v1/submissions
submissions.run 
Not tested yet.
Get submission GET /api/v1/submissions/{id}
submissions.run 
Not tested yet.
Queue conflict search POST /api/v1/conflict-searches
conflicts.run 
Not tested yet.
Get conflict search GET /api/v1/conflict-searches/{id}
conflicts.run 
Not tested yet.
List scheduled exports GET /api/v1/scheduled-exports
dataexports.read

Returns export job status plus available ZIP files.

Not tested yet.
Check export file GET /api/v1/scheduled-exports/{fileName}
dataexports.read 
Not tested yet.