Cumino API access
The Cumino API is not self-serve: access is enabled per tenant after we review your use case and sign the DPA. Send the request and we reply with sandbox credentials.
What you can do with the API
The API exposes the same data and the same actions as the platform, so you can bring them into the tools you already use.
Candidates
Read profiles, pre-screening outcomes and call transcripts, and push status updates back from your ATS.
Campaigns
Create campaigns, publish openings and pull the applications collected through WhatsApp, Telegram and QR codes.
Public job listings
The list of published openings is already exposed without authentication: it is the same endpoint that powers the /lavoro pages, so you can republish openings on your own site.
Authentication
Access is bound to a single tenant and goes through the Cumino authentication service. Credentials are named and are revoked on request.
From request to production
Four steps. Timing depends mostly on the data processing review.
You send the request
Tell us what you want to integrate, at what volume and from which system. It tells us which scopes you actually need.
We review and sign the DPA
We check the use case and set roles and legal basis for processing. If you are already a customer, the DPA is often already in place.
You get sandbox credentials
A separate environment with test data, so you can build and test without touching real candidates.
You go to production
Once the integration is verified, we enable the production token with the agreed limits.
What to know first
Bearer authentication
Every call carries a token in the Authorization header. Tokens are bound to a tenant and are not shared across environments.
Rate limits
Limits are agreed per integration, based on the volumes you declare in the request, and are communicated together with the credentials.
Personal data
The API handles candidate data: a signed DPA and a documented purpose are required before credentials are issued.
Request access
We reply to the address you enter here. The technical fields let us prepare the right credentials on the first pass.
Where the technical documentation lives
The reference with endpoints, response formats and examples ships with the sandbox credentials, so it always describes the environment we enabled for you rather than a hypothetical one.