Skip to main content
POST
/
routing
/
evaluate-api
Evaluate Routing
curl --request POST \
  --url https://api.casexchange.com/api/v1/routing/evaluate-api \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "caseType": "<string>",
  "severity": 3,
  "jurisdiction": "<string>"
}
'
{
  "success": true,
  "data": {
    "firm": {
      "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "name": "<string>",
      "contactEmail": "[email protected]",
      "contactPhone": "<string>",
      "isExternalContact": false
    },
    "isActive": true,
    "rule": {
      "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "name": "<string>",
      "description": "<string>"
    }
  }
}
Evaluate routing rules to determine which firm should receive a case based on case characteristics. Use this endpoint for “preview” experiences before creating cases, or to validate routing logic.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
caseType
string
required

Case type name (required). Must match an existing case type in the system.

Minimum string length: 1
​
severity
integer | null

Case severity/tier level (1-5). Optional - if not provided, routing rules that match any tier will be considered.

Required range: 1 <= x <= 5
​
jurisdiction
string | null

Jurisdiction code. Optional - if not provided, routing rules for nationwide or all jurisdictions will be considered.

Response

Routing result

​
success
boolean
​
data
object