GET /analytics.
Sandbox
Start with fictional data using your organization API key, available in Organisation settings. Your organization needs at least one recruiter; production API access and analytics access are not required. SetCOLLECTIVE_API_KEY in your terminal or server environment, then make a request:
recruiters array to filter requests; real recruiter IDs are rejected. Fixed UTC dates give repeatable results.
Production
Ask support@collective.work to enable production API access and analytics access, then switch the URL to:Choose your report
By default: all recruiters, all sections, daily totals, last 30 UTC calendar days including today.
Match IDs to names using
recruiters; see the resolved filters in metadata.filters.
Inactive recruiters, including former members still attached to the organization, remain in the results
with zero counts where appropriate.
Usage counts events; activity counts distinct UTC days. Multiple events on one day count as
one active day. Overall activity combines days across Sherlock, searches, jobs, and messages.
- Recruiters: repeat
recruiterIdsto select multiple people. - Sections: repeat
sections, for examplesections=usage§ions=engagement. Only selected sections are returned. - Dates: choose a preset
range, or userange=CUSTOMwith inclusive UTCfromandtodates (YYYY-MM-DD). - Grouping: set
breakdowntoDAILY,WEEKLY,MONTHLY, orYEARLY.
Requests that are too complex are rejected. Shorten the timeframe, or adjust the filters or
breakdown as indicated by the error message.

