id to schedule practitioner appointments.
Your API key only returns locations within your partner access context. Use
GET /api/v1/locations to list all locations available to you.Fields
UUID for the location. Pass this as
location_id when creating an appointment.Display name for the location.
Clinic or company operating the location. May be null.
Primary street address. May be null.
Secondary address line (suite, floor, etc.). May be null.
City. May be null.
State or province (resolved via the city’s linked state). May be null when the city has no linked
state.
Postal or ZIP code. May be null.
Full country name (e.g.,
Germany). May be null.Two-letter country code per ISO 3166-1 alpha-2
(e.g.,
DE, US). May be null.IANA timezone identifier for the location (e.g.,
Europe/Berlin, America/New_York). Use this to
display scheduled times in the correct local time. May be null.Phone number for the location. May be null.
Email address for the location. May be null.
Website URL for the location. May be null.
Direct link to the location on Google Maps. May be null.
URL of a photo of the location. May be null.
Weekly opening hours for the location. Each weekday key (
monday–sunday) maps to an array of
{ open, close } time ranges in HH:MM (24h) format. An empty array means the location is closed
that day. May be null if hours are not available for the location.Availability
Theopen_hours field above describes the static weekly opening schedule. To render real bookable slots — and avoid double-booking against existing Aniva sessions — call Get Availability for the location and pass it the date window you want to display. That endpoint surfaces live slot starts (combining the location’s upstream scheduling provider with subtraction of already-booked sessions) and is the right source of truth for any booking UI.