Skip to main content
GET
Inbox summary
This report answers “what is waiting in my Inbox?”. It is a snapshot of right now, so it takes no dates. For what each teammate did over a period, use Team performance. See Inbox overview for the views in the app.

What each count means

Every count is a number of leads, grouped by the lead’s current owner. A lead counts at most once per column.

How the response is organized

Use a user_id from by_person as assigned_to in List escalations to see that person’s cases.

Filter by task

Add workflow_id to count only leads active in that task (workflow in the API).

Before you start

  • MCP keys need leads:read. Full-access REST keys need nothing else.
  • Errors return a stable code in error, such as invalid_workflow_id or workflow_not_found. Map the code to your own copy.
  • An AI connected to the Nexor MCP server reads the same counts with the get_inbox_summary tool.

Authorizations

X-API-Key
string
header
required

API key for authentication. Keys are prefixed with nxr_live_.

Query Parameters

workflow_id
string<uuid>

Task ID (workflow in the API). Counts only leads active in this task. A malformed ID returns 400 invalid_workflow_id, and a task outside this account returns 404 workflow_not_found.

Response

Current Inbox counts per teammate.

success
enum<boolean>
required
Available options:
true
workflow_id
string<uuid> | null
required

The task filter, or null for every task.

totals
object
required

Sum of every teammate row and the unassigned row.

by_person
object[]
required

One row per teammate who has at least one lead in Inbox, sorted by unanswered, then escalated_open, then name.

unassigned
object
required

Leads without an assigned teammate.

Last modified on September 29, 2026