Deel: Open API for global hiring, payroll, and HR

Deel: Open API for global hiring, payroll, and HR. Deel's Open API exposes workforce operations — contractors, employer-of-record (EOR) employees, contracts, payroll adjustments, and webhooks — so product and ops teams automate what used to live in spreadsheets and vendor UIs. Builder docs live at developer.deel.com.

Click to zoom

What you can automate

This is not a Solana program. It sits next to payments and agent stacks when a crypto-native company still has to hire humans legally in many jurisdictions — the same gap Visa/Mastercard/Deel-style APIs fill for ops engineers.

Base URL and auth

REST is documented as OpenAPI 3.0.1. Calls go to Deel's REST host (commonly https://api.letsdeel.com/rest/… — confirm the current base path in the Developer Center). Authenticate with a bearer API key from the Developer Portal.

export DEEL_API_KEY="…"

# Example shape from Deel docs — create a contractor contract
curl -sS -X POST "https://api.letsdeel.com/rest/contracts" \
  -H "Authorization: Bearer $DEEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "data": {
      "title": "Senior Backend Engineer",
      "type": "ongoing_time_based",
      "country_code": "GB",
      "start_date": "2026-02-01",
      "worker": {
        "first_name": "Alex",
        "last_name": "Rivera",
        "expected_email": "[email protected]"
      },
      "compensation_details": {
        "amount": 8000,
        "currency_code": "GBP",
        "frequency": "monthly"
      }
    }
  }'

Treat keys like production secrets: server-side only, rotate on staff change, scope to the minimum environment (sandbox vs production when offered).

Integration patterns

MCP surface

Deel documents MCP alongside REST and webhooks on the developer home. That matters if you already run agent tooling (Cursor, custom MCP hosts, x402-paid tools): workforce actions become tools with the same audit expectations as any other privileged integration — least privilege keys, human approval for irreversible steps (terminate, large off-cycle pay), and logging of every tool call.

Pairing note: if you monetize internal MCP tools, stacks like MCPay address pay-per-call; Deel MCP is the domain side (HR/payroll), not the payment rail.

Webhooks

Prefer webhooks over polling for contract status, onboarding completion, and payment events. Verify signatures if Deel provides them; idempotent handlers; dead-letter queue for failed deliveries. Map Deel worker IDs to your internal user IDs early so access systems and payroll never diverge.

Limits and non-goals

• Not a replacement for local employment counsel — EOR coverage and contract types still depend on country rules Deel supports.
• Endpoint coverage grows over time; always check the live OpenAPI reference before assuming a field exists.
• No on-chain settlement here — for crypto payroll rails you still bridge out to your payments stack after Deel's fiat/ops layer.

People and links

Resources

• Build custom HR and payroll solutions — Deel API
• Quickstart
• How to use Deel API (help center)
• MCPay — x402 for MCP servers