Retrieve employee profiles and custom field data from the Namely API
domain: developers.namely.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth 2.0 access token by completing the authorization code flow via your Namely subdomain (https://{company}.namely.com/api/v1/oauth2/authorize).
Call GET /api/v1/profiles to retrieve all employee profiles; the response includes a profiles array with standard and custom fields.
Call GET /api/v1/profile_fields to retrieve the schema of all profile fields at your company, including custom fields — this shows valid field keys and their expected formats.
To retrieve a specific employee, call GET /api/v1/profiles/{id} using the profile ID from the directory listing.
Custom fields appear as keys at the bottom of each profile object; use the profile_fields schema to interpret their structure and valid values.
Known gotchas
Custom field keys in profile objects are client-specific — always fetch /api/v1/profile_fields to understand the field schema for a given Namely account rather than hardcoding field names.
The Namely API uses OAuth 2.0 with per-company subdomains — the token and API base URL are specific to each company subdomain; a multi-tenant integration must manage separate tokens per customer.
Namely's API may return paginated results for large employee directories; check for pagination metadata in the response and follow next-page links rather than assuming a single response contains all records.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?