Docs · Connect your tools
Connect Deel
StackWeaver reads, and never changes, one read-only endpoint on your Deel account once a day, through an API token you create yourself. This guide says exactly what is read, which permission the token needs, how to create one, and how to remove it.
Last reviewed: 6 November 2026 · Describes what is live in production on that date. A result is evidence of what the provider returned at a time, nothing more.
1. What it collects
Once a day StackWeaver calls Deel's API with the token you paste. The result is kept as an Evidence Object with a SHA-256 fingerprint (platform), including a result that fails.
| Check (as shown in the portal) | What it looks at |
|---|---|
| API token valid and reachable | Whether the stored token is accepted and your organisation's contracts list responds. Only the count of contracts is kept. Evidence only: no threshold is applied. |
2. What it does not do
- It never reads a worker's name, pay or contract detail. The one check reads only how many contracts exist, never their contents.
- It cannot change anything: the token is used for one read-only endpoint.
- It does not say your HR or contractor-compliance programme meets any requirement. A result is what Deel returned at a certain time.
- It works against either a sandbox or a production Deel token; you say which when you connect — Deel issues separate keys per environment and never accepts one in the other (Deel).
3. The access it needs
One credential: an API token, sent as a Bearer token in the Authorization header on every request (Deel).
Who can connect. In StackWeaver, a workspace owner or admin pastes the token. Deel does not tell StackWeaver who created the token or what role they hold, so create it with no more access than this one read-only check needs.
4. Connect steps
- In Deel's dashboard, open Developer/API settings and create an API token.
- In StackWeaver, open Evidence, the Deel section, and paste the token. Type "sandbox" in the environment field for a staging token, or leave it empty for a production token.
- Press Test connection. StackWeaver records the result and fills in the account fingerprint automatically.
5. Reading the results
| Label | What it means |
|---|---|
| Pass | The provider returned data that meets the threshold at that time |
| Fail | The provider returned data that does not meet the threshold |
| Not enabled | There was nothing to check, or the feature needs a plan StackWeaver could not confirm |
| Could not check | StackWeaver could not read the data, or the check needs a higher plan than the account has |
6. Disconnect and revoke
- In StackWeaver, press Disconnect on the Deel section. StackWeaver deletes the stored token.
- In Deel's dashboard, revoke or delete the token yourself — StackWeaver has no way to ask Deel to revoke a token on your behalf.
What remains. Past evidence stays in your workspace as the audit trail. Disconnecting does not delete it.
7. Troubleshooting
| Message | What to do |
|---|---|
| Deel refused the token: it may be wrong or revoked | Check the token was copied in full, and that the environment field matches the token (sandbox tokens only work against a sandbox connection; production tokens only against a production one) |
| This token belongs to a different Deel account than the one already connected here | Disconnect first if you mean to switch to a different Deel account |
Still stuck? Use the contact page.
Sources and method
Statements about GitHub and Okta link to their own documentation. Statements about StackWeaver link to the page that says them, or are recorded in a claims ledger with the file in StackWeaver's repository that they come from. See oureditorial policy. Spotted an error? Use the contact page.