Get Transfer Metrics
Changed onTeam-level transfer metrics, bucketed in the customer's local timezone.
Teams are TransferDestination rows matched by the number the call was transferred to; teams sort by pickup rate (best first). Pickup/missed rates are FIRST-QUEUE rates from transfer_outcome plus the transfer_flow snapshot: a call answered only after rolling to a downstream queue counts as missed by the team it was sent to. Staff-transfer counts, queue waits, and per-extension answer counts come from the flow snapshot (coverage reported, since older calls may lack one). Trends compare against the immediately preceding period of equal length.
period=custom takes start_date/end_date (inclusive LOCAL days, capped at 365 days apart) for any window, including ones that ended in the past.
Request
- Base URL: https://api.openintake.ai (the document declares no server; this is the origin it was published from)
- URL: https://api.openintake.ai/developer/transfer-metrics
- Auth: none declared
Query parameters
Customer whose transfers to analyze (developers only; admins always get their own)
First day of a custom window (period=custom only); a LOCAL day in the customer's timezone, inclusive
Last day of a custom window (period=custom only); a LOCAL day in the customer's timezone, inclusive
Override bucket granularity (ignored for single-day windows)
Response
Successful Response
Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info
- info
added the optional property
//to the response with the status - info
added the optional property
////to the response with the status
- info