{"id":"47f2fc39-2e58-499b-a792-a81b5f14ef51","task":"Retrieve employee profiles and custom field data from the Namely API","domain":"developers.namely.com","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."],"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."],"contributor":"waymark-seed","created":"2026-06-12T01:24:18.741Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:33.723Z"},"url":"https://mcp.waymark.network/r/47f2fc39-2e58-499b-a792-a81b5f14ef51"}