remote-api-auth
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).
Install
With your agent
Install OMGSkills skill "remoteoss/remote-for-ai:skills/remote-api-auth" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/remoteoss/remote-for-ai /tmp/remote-for-ai && ln -s /tmp/remote-for-ai/skills/remote-api-auth ~/.claude/skills/remote-api-authFrom README
Remote API Auth Covers every credential and token-acquisition path for code that calls the Remote.com REST API: static customer tokens, and all four partner OAuth 2.0 flows. Invoke This Skill When Setting up Remote API access for the first time (customer or partner). Choosing between customer (API token) and partner (OAuth 2.0) auth. Implementing or refreshing any of the four partner flows: clientcredentials, authorizationcode, refreshtoken, or JWT bearer assertion. Obtaining company consent (sending a company admin through the authorizationcode flow). Selecting the right environment host for sandbox vs. production. Resolving a 401 or 403 response traced to auth or scopes. For the in-editor Remote MCP session, the host plugin handles OAuth — this skill is for tokens your own service uses. Prerequisites Customer integrations: A Remote account with admin or owner permissions to generate an API token under Company Settings -> Integrations & APIs -> Remote API -> Generate API Token.
More from this repo
remote-api-forms
Used to build and validate request bodies for Remote.com's dynamic JSON-Schema form endpoints - the schema-first...
remote-api-integration
Used to build integrations that call the Remote.com REST API (developer.remote.com) - global HR/payroll/EOR.
remote-api-webhooks
Receive and verify Remote.com webhooks in an integration.