White-label EOR · EOR API
What does the partner API let you build into your own product?
Partner API access, set up with Teamed’s integration team: your platform sends sign-ups, new hires and changes; Teamed sends back status and data in real time.
It is not a self-serve public developer API, and /integrations says the same. If you need public reference documentation today, Deel and Remote publish theirs.
Last updated
- Platforms supportedHR, payroll and finance systems Teamed already works with.Source: teamed.global/integrations · verified 22 September 2026
- 500+
- Documented pagesPlatforms with their own page on the Integration Ledger, limitations included.Source: teamed.global/integrations · read at build
- 19
- Platform uptimeThe platform your clients run on, under your screens.Source: teamed.global/technology · verified 8 October 2026
- 99.97%
- CountriesWhere Teamed can employ someone on behalf of your clients.Source: teamed.global/countries · verified 11 September 2026
- 187+
What does the partner API move, and what does it not?
Four flows today. Your platform sends what your client did in your screens; Teamed sends back what changed underneath, as it changes. The last column says where a person still steps in.
Partner API ledger
What moves, and what does not
| Flow | What your platform sends | What Teamed sends back | What still needs a person | Verified |
|---|---|---|---|---|
| Client sign-up | A new client, created in your sign-up screens. | The client’s status, as it changes. | Nothing by default. Teamed’s team speaks with the client where a hire needs a person. | 2026-10-15 |
| New hire submitted | The hire, from your hire form. | The hire’s status and data, in real time, as onboarding runs. | Confirming requirements and getting the hire moving: Teamed’s team speaks directly with your client. | 2026-10-15 |
| A change to an existing employee | The change, from your client dashboard. | The updated status and data, in real time. | Where the change needs a person, Teamed’s team speaks with your client. | 2026-10-15 |
| Status and data flowing back (webhooks) | Nothing. This is Teamed sending to you. | What has changed, as it changes, so your screens stay current. | Nothing. This is the automated flow. | 2026-10-15 |
| Everything else: payslips, time off, expenses, documents and contracts, cost quotes, offboarding, employee self-service | Not published yet | Not published yet | Confirmed with your tech team before you build | 2026-10-15 |
Source: Teamed, white-label EOR partner offer, verified 15 October 2026. The field-level detail in every cell, and every flow in the last row, is confirmed with your tech team before you build and published here once it is.
What is the sandbox?
A sandbox with simulated EOR data. Your engineers build and test against it before anything is live, with guidance from Teamed's team on how to use the APIs.
How do we get access and support while we build?
Through the partnership: partner API access, guidance from Teamed's team on the APIs, and a dedicated Teamed team for the phased rollout with your tech team. How it works sets out the sequence from the first conversation to your first client live.
What still needs a person?
Confirming requirements and getting a hire moving. Where a hire needs a person, Teamed's team speaks directly with your clients. Everything the ledger does not list as moving through the API is handled by that team until it is published here.
What the ledger leaves blank, and why
The blank cells are the point. Publishing a flow without evidence behind it would be a claim Teamed cannot stand behind, and an engineer would find the gap the day they got sandbox access. So the ledger lists the four flows the offer holds today, says plainly what is not published yet, and grows as each flow is confirmed with a partner's tech team. The Integration Ledger works the same way for the platforms Teamed connects to.
Build EOR into your product.
A partnerships lead sets up a working session with your team.
Talk to partnerships