Skip to content
FibonacciAestheticsLog inTry it free

For developers

Connect your program to Fibonacci

The APIs are open, in FHIR R4 with OAuth 2.0. The practice decides what your program can read and can revoke its access whenever it wants.

The screen of a laptop with coloured code.
The Fibonacci brand for aesthetic medicine: a white folder with the golden spiral on a blue square.
Access for external programsTight permissions, decided by the practiceFHIR R4, no clinical data

Authentication

How to get in: two ways

Practice key

Who can use it: a practice, for its own program or for a vendor working for it. It is created by the practice administrator, and the feature is enabled on request.

Three permissions, which add up: read-only calendar, appointment requests, and patient contact details.

The secret is shown only once and the token lasts one hour.

curl -s -X POST "https://app.fibonaccimedica.it/api/oauth2/token" \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'grant_type=client_credentials' \
  --data-urlencode "client_id=$CLIENT_ID" \
  --data-urlencode "client_secret=$CLIENT_SECRET"

Registered app, with the practice’s consent Coming soon

Who can use it: a company that makes a product for many practices. We register it, one by one, and each practice connects it with a click.

Five fixed permissions: read and write calendar, appointment requests, contact details, and read invoices without line items.

No shared secret: the JWT is signed with your private key and lasts at most five minutes.

curl -X POST "$TOKEN_URL" \
  -d grant_type=client_credentials \
  -d client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer \
  -d client_assertion="$JWT"

No clinical data passes through. Medical history, visits, treatments, photos, consents and invoices stay out, whatever permission the practice chooses: asking for them returns 403.

Quick guide

Five steps for the first call

  1. You tell us what your program does

    From the Partner page, with the permissions you need.

  2. The practice activates access

    Whoever administers it creates a key, or connects your registered app.

  3. Request the token

    It lasts one hour: request it once and reuse it.

  4. You call the FHIR R4 API

    Only on the addresses of the practice that gave you access.

  5. Receive notifications

    A signed message when an appointment is created, changes, or is cancelled.

Examples

Read free slots and receive notifications

The complete technical guide, with all the answers and errors, goes to whoever the practice has put in charge.

Read the open slots

curl -s -H "Authorization: Bearer $TOKEN" \
  "https://app.fibonaccimedica.it/api/fhir/R4/Slot?schedule=Schedule/$AGENDA&status=free&_sort=start"

The notification that arrives at your program

POST /notifiche HTTP/1.1
Content-Type: application/json; charset=utf-8
X-Fibonacci-Firma: t=1781342400,v1=9f2c…

{
  "evento": "appuntamento.creato",
  "appuntamento": { "stato": "booked", "inizio": "2026-11-20T09:00:00Z" },
  "riferimenti": { "paziente": "Patient/…", "operatore": "Practitioner/…" }
}

The X-Fibonacci-Firma header carries the time and the signature of the body: you verify it with the secret that the practice sees only once.

Without writing code: Zapier, Make, n8n, and MCP use the same accesses, with the same keys. Today's connections

Frequently asked questions

The questions of whoever writes the connection

Which standards do you use?

FHIR R4 for data and OAuth 2.0 with client credentials for access. Notifications are signed JSON.

Can I search patients by surname?

No. Patient and appointment lists cannot be searched: a search by surname would reveal the surname anyway. Codes reach you with notifications or from the slots.

What happens if the practice revokes the key?

The token you have stops working immediately, not at expiry, and you can no longer request a new one.

Are there request limits?

Yes. The token lasts one hour: request it once and reuse it. Beyond the limit the token endpoint answers 429.

Do I need a contract with the practice?

As a rule yes: a program that processes this data on behalf of the practice is a data processor, and you need the Article 28 GDPR agreement between you and the practice.

Do you want to connect your product to Fibonacci?

Write to us about what it does and which data it needs. We design the connection together.