Remote (via Apideck)

Access Remote 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 Remote plumbing.

Beta connector. Remote is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: remote
• Unified API: HRIS
• Auth type: apiKey
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Remote docs: https://developer.remote.com
• Homepage: https://remote.com/

At a glance

• Implementation difficulty: moderate — API Token Authentication - Each Consumer Generates Their Own Token in Remote
• Vendor partnership required: no — Nothing has to be registered with Remote to use this connector.
• Apideck-managed credentials: not available — Each consumer supplies their own Remote API token.
• Account type required: Remote company account (any plan).
• Consumer access level: A company admin or owner, since only those roles can generate an API token in Remote.
• Sandbox: available (signup) — Free on request from Remote: they email a pre-seeded demo company and a test token, no sales conversation. Access runs for 14 days.
• Costs: Free. Remote charges nothing extra for API access, and sets no limit on the number of connections you create.
• Rate limits: 300 requests a minute for each company.
• Authentication: API token, sent as a bearer token.

Important to know:

• A token belongs to one Remote company and to one environment. Production tokens begin ra_live_ and sandbox tokens begin ra_test_, and the environment selected when connecting must match the token, or the connection fails.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/remote (overview field) is the live, authoritative version.

When to use this skill

Activate this skill when the user explicitly wants to work with Remote — for example, "sync employees in Remote" or "list time-off requests in Remote". This skill teaches the agent:

1. Which Apideck unified API covers Remote (HRIS)
2. The correct serviceId to pass on every call (remote)
3. Remote-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, or apideck-rest

For the raw OpenAPI spec:

• HRIS: https://specs.apideck.com/hris.yml · API Explorer

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 Remote
const { data } = await apideck.hris.employees.list({
  serviceId: "remote",
});

Portable across 58 HRIS connectors

The Apideck HRIS unified API exposes the same methods for every connector in its catalog. Switching from Remote to another HRIS connector is a one-string change — no rewrite, no new SDK.

// Today — Remote
await apideck.hris.employees.list({ serviceId: "remote" });

// 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 Remote 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: API Key
• Managed by: Apideck Vault — the user pastes their Remote API key into the Vault modal; Apideck stores it encrypted and injects it on every request.
• Rotation: if the user rotates their key, they re-enter it in Vault. No code changes needed.

Setup guide: Apideck publishes a step-by-step guide for registering an OAuth app / configuring credentials for Remote — see https://developers.apideck.com/connectors/remote/docs/consumer+connection. Use that as the authoritative source when walking users through connection setup.

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/remote' \
  -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 Remote directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Remote'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: remote" \
  -H "x-apideck-downstream-url: <target endpoint on Remote>" \
  -H "x-apideck-downstream-method: GET"

See Remote'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

• Apideck connection guide for Remote
• HRIS OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Remote official docs