Integrate in an afternoon
Two headers, a public OpenAPI document, and a handful of REST endpoints — no sandbox to configure, no SDK to wait on us for.
Get your keys
Sign in to your vendor dashboard, or request access if you're new — you'll get a separate key for dev and prod.
Set two headers
x-api-key and x-api-env on every request. There's no default environment, so a request without it is rejected rather than silently reaching production.
Generate a typed client
The OpenAPI 3.1 document is public and needs no key, so you can generate a client before access is even granted.
Call your first endpoint
Start with a read — campuses or care centres — then work through the recipes for the flow you're building.
Your first call
A plain read, no body — the two headers are the only thing every request needs beyond a normal REST call.
GET /v1/campuses
curl https://partners-api.cadabamscare.in/v1/campuses \ -H "x-api-key: <your key>" \ -H "x-api-env: dev"
Generate a client
The OpenAPI document is derived from the live service, not written by hand, so it can't drift from behaviour. Pick a language and generate a typed client before access is even granted — generators just don't know about the two headers, so set those in the client's default header config yourself.
npx @openapitools/openapi-generator-cli generate \ -i https://partners-api.cadabamscare.in/openapi.json \ -g typescript-fetch \ -o ./partner-api-client
Reads from the public spec at https://partners-api.cadabamscare.in/openapi.json — no key needed to generate a client, only to call the API with it.
Need to know
x-api-key + x-api-env
Issued per environment. A dev key never touches production, and there is no default env to forget.
All times in IST
Every timestamp is India Standard Time, offset-aware ISO 8601. No conversion needed on your side.
Strict by default
Unknown or mistyped fields are rejected with a 422 naming them — never silently dropped.
Hosted payments
Razorpay handles cards, UPI, netbanking and wallets. Card data and payment credentials never touch your systems.
Ready to call your first endpoint?
Sign in to your dashboard for keys, or walk through a full flow in the recipes.