Namely REST API access for reading employee profiles, job titles, and teams for a connected Namely company.
Namely REST API access for reading employee profiles, job titles, and teams for a connected Namely company. Use when an agent needs employee directory or profile data from Namely. Routes through Pipedream Connect; each company lives on its own Namely subdomain, which Pipedream resolves, and Lava holds no Namely token.5 example endpoints available through Lava’s AI Gateway. See the Namely API docs for full documentation.
This provider requires your own credentials — connect your API key or OAuth account before use.
This is a catch-all provider — any valid URL under https://company.namely.com is supported. Namely REST API v1. Each company lives at https://{company}.namely.com; the literal host company.namely.com always works because the gateway routes by path and Pipedream resolves the connected subdomain. Reads under /api/v1: /api/v1/profiles (employees), /api/v1/profiles/{id} (one), /api/v1/profiles/me (the current user, an identity probe), /api/v1/job_titles, /api/v1/groups. Pagination is page and per_page (default 30); responses carry meta.total_count. Auth is brokered by Pipedream, do not send an Authorization header. This provider is read-only: only GET requests are supported. The endpoints below are curated examples.
