Remote.com

Authenticate to the Remote.com REST API and obtain access tokens for an integration. Use when setting up API access, choosing between customer (API token) and partner (OAuth) auth, implementing the four partner flows (client_credentials, authorization_code, refresh_token, JWT bearer assertion), getting company consent, picking the environment/base host, handling token lifecycle/refresh, or resolving 401/403 errors. Do NOT use for the in-editor Remote MCP session (browser OAuth, handled by the host plugin), endpoint discovery (remote-api-integration), form bodies (remote-api-forms), onboarding (remote-api-onboarding), or webhooks (remote-api-webhooks).

Build and validate request bodies for Remote.com's dynamic JSON-Schema form endpoints - the schema-first mechanism behind most REST writes. Use when fetching a form schema (GET /v1/countries/{country_code}/{form}, /v1/companies/schema, /v1/contract-amendments/schema, and similar), honoring required/enum/oneOf/if-then-else, handling conditionally-forbidden fields or x-jsf-* presentation/currency, or 422 validation on any form-driven write - company creation, personal-details, contract amendments, terminations, contractor onboarding, legal-entity details, benefits. For the multi-form hire sequence use remote-api-onboarding. Do NOT use to operate via the MCP, for auth (remote-api-auth), endpoint discovery (remote-api-integration), or webhooks (remote-api-webhooks).

Build integrations that call the Remote.com REST API (developer.remote.com) - global HR/payroll/EOR. Use when finding the right endpoint or scope, reading an endpoint's contract, calling REST endpoints, encoding money/dates, paging, or handling errors and rate limits - the entry point and router for any Remote REST integration task. Do NOT use to operate your own workspace (use the Remote MCP operator skills), to obtain tokens (remote-api-auth), to build a dynamic-form body (remote-api-forms), to run the hire sequence (remote-api-onboarding), or for webhooks (remote-api-webhooks).

Hire/onboard employees and contractors through the Remote.com REST API - the multi-form sequence built on remote-api-forms. Use when creating an employment (hire/onboard): the basic-information then address then personal-details then contract then pricing sequence (POST then PATCH then invite), and the EOR vs Global Payroll vs contractor variants. For generic form mechanics and non-hire form writes (amendments, personal-details, company creation) use remote-api-forms. Do NOT use to operate via the MCP, for auth (remote-api-auth), or webhooks (remote-api-webhooks).

Receive and verify Remote.com webhooks in an integration. Use when subscribing to events (POST /v1/webhook-callbacks), building a receiver, verifying the X-Remote-Signature HMAC, parsing the flat event payload, deduping/idempotency, or choosing which event_type to listen for. Covers HMAC-SHA256 hex over raw_body + ':' + millisecond timestamp. Do NOT use to operate via the MCP, for auth (remote-api-auth), outbound API calls (remote-api-integration), or form writes/onboarding (remote-api-forms / remote-api-onboarding).