At a glance
- Availability: Experimental (how to enable).
- Authentication: API key.
- Connection: The key from
DEEL_API_TOKENis sent as theBearerprefixedAuthorizationheader. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.Setup
- Generate an API token: Sign in to the Deel app (https://app.deel.com), open Apps & Integrations and go to the API access / developer section, then click Generate new token. Choose an organization token (recommended for automation; never expires and is not tied to a user) or a personal token, and select the scopes the tools need: contracts:read, people:read, accounting:read, timesheets:read, and timesheets:write if you want to submit timesheets.
- Optional: use the sandbox for testing: Deel provides an isolated sandbox with sample data that never triggers real payments or contracts. Create a sandbox account from the developer center in the Deel platform (sandbox app at demo.letsdeel.com) and generate a sandbox token there. The sandbox API base URL is https://api-sandbox.demo.deel.com/rest/v2 - to test against it, point a copy of this connector at that host.
- Set the environment variable: Add DEEL_API_TOKEN to your .env with the generated token.
- Verify access: Run List Contracts. If you get a 403, check that the token includes the required scope for the endpoint.
Provider notes
- All requests must be made over HTTPS; the token is sent as Authorization: Bearer <token>.
- Personal tokens are limited to what the generating user can access and expire when that user leaves the organization; organization tokens do not expire.
- This connector targets the production API (api.letsdeel.com). Sandbox and production use separate credentials.
Tools
Verify the connection
Call a read tool such asdeel__list_contracts with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.