namely
Namely integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, pa
SKILL.mdskills/namely/SKILL.md
GitHubNamely (via Apideck)
Access Namely through Apideck's HRIS unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Namely plumbing.
Quick facts
- Apideck serviceId:
namely - Unified API: HRIS
- Auth type: oauth2
- Gotchas: page
- Namely docs: https://developers.namely.com
- Homepage: https://www.namely.com/
At a glance
- Implementation difficulty: moderate — Partner Enquiry or Admin Access Needed for OAuth Credentials
- Vendor partnership required: no (developer portal) — Namely's partner page takes integration enquiries at hello@namely.com.
- Apideck-managed credentials: not available — Apideck holds no Namely OAuth app.
- Account type required: Paid Namely account with API access enabled.
- Consumer access level: A Namely administrator, or a user an administrator has granted API access.
- Sandbox: not available — Test against a live Namely account; Namely documents no public route to request a sandbox tenant.
- Rate limits: 100 requests per minute on GET /profiles.
- Authentication: Authorization Code flow.
- Webhooks: Virtual webhooks - employee created, updated and terminated events.
Important to know:
- You connect Namely with your own OAuth client ID and secret. Sources disagree on whether a tenant admin can create these directly or they come through Namely's partner route, so confirm the route with Namely before you plan around it.
Facts synced from Apideck's connector metadata API —
GET /connector/connectors/namely(overviewfield) is the live, authoritative version.
When to use this skill
Activate this skill when the user explicitly wants to work with Namely — for example, "sync employees in Namely" or "list time-off requests in Namely". This skill teaches the agent:
- Which Apideck unified API covers Namely (HRIS)
- The correct
serviceIdto pass on every call (namely) - Namely-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List employees in Namely
const { data } = await apideck.hris.employees.list({
serviceId: "namely",
});
Portable across 58 HRIS connectors
The Apideck HRIS unified API exposes the same methods for every connector in its catalog. Switching from Namely to another HRIS connector is a one-string change — no rewrite, no new SDK.
// Today — Namely
await apideck.hris.employees.list({ serviceId: "namely" });
// Tomorrow — same code, different connector
await apideck.hris.employees.list({ serviceId: "bamboohr" });
await apideck.hris.employees.list({ serviceId: "workday" });
This is the compounding advantage of using Apideck over integrating Namely directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Authentication
- Type: OAuth 2.0
- Managed by: Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.
- User setup: Users authorize via the Vault modal. Connection state progresses
available → added → authorized → callable. - Token refresh: automatic. Expired tokens are refreshed transparently on the next API call.
See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Verifying coverage
Not every HRIS operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/namely' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
Escape hatch: Proxy API
When an endpoint isn't covered by the HRIS unified API, use Apideck's Proxy to call Namely directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Namely's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: namely" \
-H "x-apideck-downstream-url: <target endpoint on Namely>" \
-H "x-apideck-downstream-method: GET"
See Namely's API docs for available endpoints.
Sibling connectors
Other HRIS connectors that share this unified API surface (same method signatures, just change serviceId):
bamboohr, workday, deel (beta), hibob, personio, adp-ihcm (beta), adp-workforce-now (beta), paychex (beta), and 49 more.
See also
- HRIS OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Namely official docs