UDENTIVA API Documentation

Overview

The UDENTIVA API follows REST principles; it uses a JSON body and returns standard HTTP status codes. All requests are made over HTTPS and authenticated with an API key. Every request is scoped to the data of the clinic the key is bound to (full data isolation).

Base address:

https://api.udentiva.com

Authentication

Carry your API key in the Authorization header in requests. Keys are generated through the clinic panel and can be revoked at any time.

# Example request
curl https://api.udentiva.com/v1/patients \
  -H "Authorization: Bearer udk_live_xxx" \
  -H "Accept: application/json"

All endpoints to be opened externally are listed below. Each resource's detail page contains parameters, an example request/response and security notes. Write endpoints support the Idempotency-Key header.

Error Format

Errors are returned in a consistent envelope; the code is for the machine, the message for the user. Internal error/stack is never leaked.

{
  "error": {
    "code": "validation_failed",
    "message": "Invalid field: email"
  }
}

Rate Limit

Requests are rate-limited per minute. When the limit is exceeded, 429 is returned; the response headers carry the remaining quota information.

Versioning

The API version is carried in the path (e.g. /v1). Backward-incompatible changes are released under a new version.

Webhook Events

As events occur at your clinic, a signed notification is sent to your registered address. This keeps your own system up to date in real time.

# Example event types
patient.created   appointment.created   appointment.status_changed
invoice.created   payment.created       lab_order.status_changed
treatment_plan.updated   lead.created   tourism_case.status_changed