Authenticate to the Remote.com API using OAuth2 client_credentials and create an employment record
domain: developer.remote.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a partner application in the Remote developer portal to obtain a client_id and client_secret
Exchange credentials for an access token: POST to https://gateway.remote.com/auth/oauth2/token with grant_type=client_credentials and an Authorization: Basic header containing Base64-encoded client_id:client_secret and Content-Type: application/x-www-form-urlencoded
Store the returned access_token; it expires in 3600 seconds — refresh proactively before expiry
Create an employment record for any employment type by posting to POST /v1/employments with the worker's personal details and employment terms
Retrieve required onboarding fields for the specific country from the Remote docs or API before submission, as required fields vary by country
Monitor onboarding status via GET /v1/employments/{employment_id} and listen for Remote webhook events to detect when the employee completes their onboarding steps
Known gotchas
Remote uses a single POST /v1/employments endpoint for all employment types (EOR, contractor, etc.) but required fields differ by type and country — missing fields return 422 errors with details
Access tokens expire in 3600 seconds; schedule token refresh every 55 minutes to avoid mid-request expiry
Sandbox credentials at gateway.remote-sandbox.com are separate from production at gateway.remote.com — never use production credentials in sandbox
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?