Get followups
Retrieve followups with filtering and pagination support. Admins and coaches can access followups for their organization/teams, while regular users can only see their own followups.
Access
Admins and coaches can list followups for their organization and teams. Regular users only see their own followups.Pagination
Uselimit (default 25, max 100) and the cursor from the previous response to walk pages. The cursor is opaque — pass it back unchanged.
Common filters
| Parameter | Use |
|---|---|
statuses | TO_DO, IN_PROGRESS, or COMPLETE |
minimumScore | Score floor (1–5, default 3) |
starred | Starred followups only |
createdAfter / createdBefore | ISO 8601 UTC window |
includeHistory | Include status changes and notes |
excludeCrmCustomer | Omit CRM customer block |
Related endpoints
Followups can also be embedded on a single recording viashowFollowups=true on Get recording details.Authorizations
OAuth access token for user-scoped requests (Authorization Code or machine-to-machine). Send header x-siro-auth-token: <oauth-access-token>. Not an organization API key.
Query Parameters
Organization id
Pagination cursor returned by the previous page. Opaque base64-encoded token; do not parse or modify.
Maximum number of followups to return per page (1-100). Default is 25.
1 <= x <= 10025
Filter by followup score equal to or greater than the minimum score. Can be between 1 and 5. Default is 3.
Filter by followup starred state. A followup can be starred via the PATCH /followups/{followupId} endpoint. Default is false.
TO_DO, IN_PROGRESS, COMPLETE Only include followups created after this timestamp (ISO 8601, UTC).
"2024-01-01T00:00:00Z"
Only include followups created before this timestamp (ISO 8601, UTC).
"2024-01-31T23:59:59Z"
10Whether to include followuphistory with the followup. Followup history returns all status changes and notes for the followup. Default is false.
Whether to exclude the CRM customer for the followup. Default is false (CRM customer is included).