domain: deel · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate a Deel API token from Settings > Integrations > API Tokens in the Deel dashboard; tokens are long-lived bearer tokens — treat them as secrets.
Set the base URL to https://api.letsdeel.com/rest/v2/ and include the header 'Authorization: Bearer {your_token}' and 'Content-Type: application/json' on all requests.
List all workers (contractors and employees) with GET /workers; use query params 'contract_type', 'status', and pagination params 'limit' and 'offset' to filter large datasets.
Retrieve a specific contract by GETting /contracts/{contract_id}; the response includes contract type, compensation, start date, and current status.
To create a contract, POST to /contracts with the appropriate payload depending on contract type — fixed, pay-as-you-go, milestone, or EOR employee — each type has a different required schema documented in the Deel developer portal.
Access invoice and payment history per contract with GET /contracts/{contract_id}/invoices; filter by 'status' to isolate paid, pending, or rejected invoices.
Known gotchas
Deel's API versioning is reflected in the base path (/v2/); v1 endpoints exist but several are deprecated — always confirm you are using the current version path for the resource you need.
EOR (employer-of-record) employee data has additional access controls tied to country-specific compliance rules; some fields are redacted by default and require additional scope or a support request to expose.
Rate limits are enforced per token; bulk fetches without pagination can trigger 429 responses — always page results and include retry logic with backoff.
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?