mocop
Browse · Docs · Guide · Analyze

Sanovia public API

API by Sanovia · rest

Access to a professional's or a structure's fiscal data, agenda and free slots with a per-integration API key (Authorization: Bearer snv_…, created on Impostazioni → Integrazioni → «API e webhook»). Amounts are integer cents (EUR). What it never does: return clinical data, notes or link tokens; return a patient's name anywhere except on a document under patients:read (visits and patients carry initials and birth year only); change anything — the one write, POST /api/v1/public/booking-requests (bookings:write), books nothing: Sanovia e-mails the patient a confirmation link and the visit exists only once the patient confirms from their own inbox. A structure's key reads its roster only. Times are ISO 8601 instants; visit and slot windows take full date-times with an offset, never a bare day. Lists use cursor pagination: pass next_cursor back as cursor until it is null. Webhooks: POST with JSON body (schema WebhookEvent) signed in the Sanovia-Signature header as t=<unix…

Endpoint: https://sanovia.app/

Verification: observed. Source: crawl.

Capabilities (12)

  • Free slots of one professional at one sede (window up to 31 days)
  • Ask Sanovia to e-mail a patient a booking confirmation link for a free slot —…
  • Business customers (committenti)
  • Issued fiscal documents (invoices receipts credit notes)
  • One issued fiscal document
  • Recorded expenses
  • The key itself: its scopes and owner type
  • Patients minimal: id initials year of birth — nothing else
  • Payments refunds and reversals recorded on issued invoices
  • Supplier e-invoices received through the SdI
  • Appointments: times status sede configured visit type patient initials —…
  • One appointment
About · Contact · Privacy