Endpoint
Authentication
Include your API key in the request header:Path Parameters
string
required
The identifier used to look up the user. Three formats are supported:
Query Parameters
string
Inclusive lower bound of the date range as an ISO date or date-time (e.g.
2024-10-01T00:00:00Z). Date-only values use UTC start of day. Defaults to UTC start of day 29 days ago.string
Inclusive upper bound of the date range as an ISO date or date-time. Date-only values use UTC end of day. Defaults to the request time.
string
Comma-separated list of source IDs to filter by (e.g.
src-1,src-2). Returns metrics only for calls associated with the specified lead sources.string
Comma-separated list of stage IDs to filter by. Returns metrics only for calls where the contact was in one of the specified pipeline stages.
string
Comma-separated list of team IDs to filter by. Useful when an agent belongs to multiple teams and you want to isolate performance for a specific one.
string
default:"all"
Filter by call direction. Accepted values:
all, inbound, outbound.Response
A successful request returns HTTP200 with a Metrics object. The Metrics shape is the same as returned by the integration-level and contact-level metrics endpoints, scoped to this user’s activity.
The
Metrics object uses the same calculations shown in the Shilo web app’s insights view. Field names and structure align with the dashboard data model.