# Authentication — Vitrify IVF Software API

> Source: https://www.vitrifysoftware.com/api-docs/docs/authentication/

> API in active development. Conventions on this page are stable; the endpoint reference and exact values marked “at launch” are published when the API ships.

The API uses an API-key model. Keys are issued per clinic or partner and identify the integration on every request. Treat a key as a secret: never embed it in browser code or public repositories.

## How keys are sent

Each request carries the key in a request header. The exact header name is to be finalised at launch and will be documented here, along with any key prefix and rotation guidance.

> Note: The private application uses cookie and session authentication for clinic staff. That mechanism is internal to the app and is not part of this API. Public integrations use API keys only.

## Getting a key

- Request early access and describe your integration.
- Approved clinics and partners are issued a key and a base URL at launch.
- Keys are scoped to your organisation and to the operational resources your integration needs.

Request access from the API early-access form on the developer landing page.