Staff & Go API
The Staff & Go API lets a partner application read and write Staff & Go HR data on behalf of a customer company, over REST and — for AI agents — over MCP. Every capability is exposed in both forms from a single definition, so a tool and an endpoint always behave identically.
Start here
| Quickstart | Obtain credentials and make your first authenticated call. |
| API reference | Every endpoint, its parameters and its responses. The scope each one needs is in the guide of its theme. |
| Changelog | Every change to the published contract, generated from the contract itself. |
Guides
| Authentication | OAuth 2.0 client credentials, scopes, and the deprecated legacy token. |
| Discovery | What your profile and the referentials tell you before you call anything else, and how to re-synchronise. |
| Companies, employees and contracts | The establishments, the people, the contracts — and the fields withheld unless you were granted them. |
| Leave and balances | Absences, what remains on each counter, and why the reason is withheld by default. |
| Worked time | Days recorded against the schedule, and why a null there is not a zero. |
| Payroll | Closures, payslips and the variable elements that feed a run — and where the amounts are not. |
| Expenses and meal vouchers | Claims line by line, currencies that must not be added, and the counts a voucher order rests on. |
| Bulk exports | Asking for a whole domain as a file, and what the seven-day window means. |
| Errors | The Problem Details contract, the error types, and what to retry. |
| Idempotency | Idempotency-Key: making a retried write safe. |
| Rate limits | Plan quotas, RateLimit headers, and handling 429. |
| Audit trail | Reviewing the calls you made, and answering a GDPR request. |
| Webhooks | Registering an endpoint, verifying the signature, handling retries. |
| Versioning | What we guarantee within a version, and how deprecation is announced. |
| Lifecycle | Beta versus GA, and the beta:access gate. |
| AI agents (MCP) | Using the same capabilities as MCP tools. |
| Client SDKs | Generated C#, TypeScript and Python clients, and what they leave to you. |
Sandbox
Integrate against the staging environment first. It runs the same code and the same contract as production, with its own credentials and its own data — nothing you do there affects live payroll.
Your Staff & Go contact provides the staging host and your sandbox credentials.