Introduction

Recruso is a cloud-based CRM for the UK temporary-recruitment sector. Agencies use it to manage the whole worker lifecycle — client bookings, worker assignment, weekly plans, timesheets, payroll and invoicing — and the CRM integrates with Sage Payroll, Staffology and Sage Accounts. Those payroll and accounts integrations belong to the CRM; nothing about them is reached through this API.

This API gives developers programmatic access to an agency’s own Recruso data — today, the agency and its branches, clients and sites, workers, and the configuration those records refer to. It is intended for developers building on behalf of an agency already using Recruso: the agency’s own team, or a technical partner the agency chooses to share credentials with. No Recruso user account is needed to call it, and the agency decides who holds credentials and when to revoke them.

What you can build

• Data exchange between Recruso and your internal systems, in both directions.
• Synchronisation of client, site and worker records with other platforms you run.
• Workflow extensions that apply your own business logic on top of Recruso’s data.

What the API deliberately does not do

Some things are managed in the Recruso UI and are not exposed here, by design:

• Agencies are not created, listed or deleted through the API. An agency is provisioned by the Recruso onboarding team, which is what guarantees correct tenant isolation, default branches, admin users and configuration templates.
• User accounts are managed in the Recruso UI, and API apps and their credentials in the Developer Console — neither through this API.
• Every request is scoped to one agency. The token you hold determines which agency’s data you see; you never pass an agency identifier yourself, and there is no way to reach another tenant’s data.

Financial core

Bookings, plans, timesheets, payroll and invoicing are core to Recruso as a product, but they are not yet part of this API’s published surface. The concepts are described under Concepts so the domain makes sense; the endpoints will appear in the reference when they ship.

Where to go next

1. Authentication — obtain a token and make your first authenticated call.
2. Environments and base URLs — where to send the request, and why there is no sandbox.
3. Responses and pagination — the conventions every endpoint follows.
4. Errors — the error bodies, and what causes each status.
5. Domain model — the entities you will be working with.
6. The guides — complete tasks, end to end.
7. How to read the reference — then the reference itself.

You can also fetch the machine-readable contract directly at /openapi/v1.json, and read more about Recruso the product at recruso.co.uk.