A clean REST API, webhooks and SDKs.
The Vetra API gives you programmatic access to claims, eligibility, authorizations and settlements — secured by scoped keys and RBAC.
Authentication
Every request carries a bearer token and a tenant header. Scoped keys are issued per environment from Settings → API keys.
bash
curl https://api.vetrainsure.com/v1/claims \ -H "Authorization: Bearer $VETRA_API_KEY" \ -H "x-tenant-id: tnt_hygeia"
Settings → API keys with two scoped keys (sandbox + production) and their permission ranges
Screenshot — coming soon
Conventions
- Resource-oriented endpoints with predictable plural names.
- Cursor pagination — every list response returns a
page.nextcursor. - Idempotency keys for safe retries on writes.
- ISO 8601 timestamps and amounts in minor units (kobo / cents).
Core endpoints
| POST /v1/claims | Submit a claim. |
|---|---|
| GET /v1/claims | List claims (filter by status, dates, provider, member). |
| GET /v1/claims/:id | Fetch a single claim with line items, queries and attachments. |
| POST /v1/authorizations | Request a pre-authorization. |
| GET /v1/eligibility/:memberId | Eligibility verdict for a Vetra Member ID. |
| GET /v1/settlements | List settlement runs and remittances. |
Sample response
json
{
"data": [
{
"reference": "CLM-24817",
"providerName": "St. Nicholas Hospital",
"memberId": "HYG-DNG-00234-PR",
"amount": 48500000,
"status": "IN_REVIEW",
"risk": "MEDIUM"
}
],
"page": { "next": "clm_24816" }
}Webhooks
Signed webhooks are pushed for every state change.
claim.received/claim.queried/claim.approved/claim.rejected/claim.settledpa.approved/pa.rejected/pa.appealedsettlement.run.created/settlement.proof.uploadedai.risk_event.recordedfor new fraud flags.
Signature verification
Verify the
X-Vetra-Signature HMAC against the raw body using your webhook secret before trusting the payload.SDKs
- Node / TypeScript:
@vetra/sdk-node - Python:
vetraon PyPI - OpenAPI 3.1 spec available on request — generate clients in your language of choice.