List escalations
List the cases where an agent asked a person for help, filtered by status, teammate, task and date, with the question, the reason and the outcome.
Choose the status
status is pending while the case is open, and resolution_outcome says how it closed, for example resolved_manually or discarded.
Filter the list
assigned_to in the response is the lead’s owner today, not at the time of the escalation.
Page through results
limit goes from 1 to 100 (default 25) and offset skips rows. total is the number of cases that match the filters across every page.
Before you start
- MCP keys need
leads:read. Full-access REST keys need nothing else. - This endpoint only reads. To reply to or close a case, use Inbox.
- Errors return a stable code in
error, such asinvalid_statusorinvalid_limit. Map the code to your own copy. - An AI connected to the Nexor MCP server reads the same list with the
list_escalationstool.
Authorizations
API key for authentication. Keys are prefixed with nxr_live_.
Query Parameters
open: waiting for a person. overdue: open and past the expected response time. resolved: every closed case, whatever the outcome. all: every case.
open, overdue, resolved, all Only escalations whose lead is currently assigned to this user ID. Cannot be combined with unassigned_only.
true returns only escalations whose lead has no assigned teammate.
Task ID (workflow in the API). Only escalations raised by this task. A malformed ID returns 400 invalid_workflow_id, and a task outside this account returns 404 workflow_not_found.
Only escalations created at or after this time. Accepts YYYY-MM-DD (read as midnight UTC) or an ISO 8601 date-time.
Only escalations created at or before this time. Accepts YYYY-MM-DD (read as midnight UTC) or an ISO 8601 date-time.
Page size.
1 <= x <= 100Rows to skip.
x >= 0Response
A page of escalations and the total that match.
true The status filter applied.
open, overdue, resolved, all Escalations that match the filters, across every page.
x >= 01 <= x <= 100x >= 0