List compliance documents of a worker contract
Lists the compliance documents the authenticated worker has to satisfy on one of their Global Payroll contracts, together with what has already been submitted against each one. Use it to see what is still outstanding before payroll. Requirements with nothing submitted are included, with an empty filenames array and null timestamps. Retired requirements are excluded, except a retired I9, which stays listed while it can still be submitted. Only Global Payroll contracts are supported.
Token scopes: worker:read
Authentication
Authentication
The Deel API uses bearer tokens to authenticate requests. All API calls must be made over HTTPS — calls over plain HTTP or without authentication will fail.
curl -X GET 'https://api.letsdeel.com/rest/v2/contracts' \
-H 'Authorization: Bearer YOUR-TOKEN-HERE'
Standard OAuth2 security scheme based on https://swagger.io/docs/specification/authentication/
Path parameters
Query parameters
Opaque next_cursor value from the previous response, passed back unchanged. Omit for the first page.
Response
Compliance documents returned successfully. created_at and updated_at come from the submission; created_at carries the same value as uploaded_at, and all three are null until something is submitted against the requirement. The language of name and description follows the language preference of the authenticated worker. It cannot be selected per request, and the same document may read differently for two workers of the same organization. Text falls back to English when no published translation exists for that language. total_count, has_more and next_cursor always describe the whole set of requirements for the contract rather than an estimate. next_cursor is an opaque token: pass it back unchanged and never construct or parse one. The set is small — expect tens of documents for one contract, not thousands.
Opaque token to pass as cursor to fetch the next page. Null on the last page. Never construct or parse one.