API upgrades
Keep track of changes and upgrades to the Server API.
Your API version controls the API you see (for example, what properties you see in responses, what parameters you’re permitted to send in requests, and so on).
When a breaking change is introduced to the Server API, a new dated version is released and your calls to the API are not affected as long as you don't change the version you want to query (see versioning).
Below a list of all available versions of the Server API (each date corresponds to version), and their associated breaking changes.
If you’re looking for all API additions and updates, check out our Changelog page.
2023-03-28
2023-03-28
- Create new version
2023-03-28
- In The Availability object,
supported_modes
no longer return an array of enum ['NABLA_VIDEOCALL'
,'EXTERNAL_VIDEOCALL'
,'IN_PERSON'
] but an array of enum containing only 2 values:'VIDEOCALL'
or'IN_PERSON'
- In Create an availability, the
supported_modes
property, in body params, can be set with an array of enum containing 2 possible values:'VIDEOCALL'
or'IN_PERSON'
2023-03-13
2023-03-13
- Create new version
2023-03-13
- Providers are no longer updated in conversation updates.
2023-02-16
2023-02-16
- Remove
description
field from allergies, conditions, immunizations, medication statements and procedures in POST and PATCH requests and in corresponding response objects.
2023-02-08
2023-02-08
- Multiple assigned providers per conversation instead of only one.
- Update the get conversation endpoint to return an
assigned_providers
field being a list of provider instead of a singleassigned_provider
. - Update the create conversation endpoint to accept an
assigned_provider_ids
field instead of a singleassigned_provider_id
. - Update the update conversation endpoint to accept an
assigned_provider_ids
field instead of a singleassigned_provider_id
. - Add
EXTERNAL_VIDEOCALL
mode
to theAppointment
object. - Add
external_videocall_url
to theAppointment
object.
2023-01-27
2023-01-27
- Appointment
url
is now a child of theAppointment
object
instead of being a sibling in the response body of the Create Appointment endpoint. - Phone numbers format in patient and provider objects are updated and prefixed, from this version, with the '+' sign and still following the E.164 ITU recommendation
2022-12-20
2022-12-20
2 parameters are renamed in this version:
- Deprecate
text
andattachment
in Message create and replace them withcontent
, a composite type that can be either a text or an attachment (but not both at the same time) - In QuestionnaireResponses create and update operations,
data
parameter is renamed intoitems
. - In Patient create and update operations,
patient_field_values
parameter is renamed intocustom_fields
.
2022-12-14
2022-12-14
This version deprecates the support of updates via HTTP PUT
requests. From that point, any update needs to be made with an HTTP PATCH
request.
2022-10-19
2022-10-19
With this version, conversations can contain multiple patients and this change introduce the following breaking changes:
-
The conversation object:
- The
patient
field is deprecated and replaced bypatients
, which contains the list of patients included in the conversation
- The
-
Create a conversation, in body params:
patient_id
is deprecated and replaced bypatient_ids
, which contains the list of patients included in this conversation.- A new field is required,
type
, to categorize the conversation with 2 possible values:individual_conversation
, when there's a single patient with one or several practitionersgroup_conversation
for conversation with several patients.
2022-07-11
2022-07-11
First version of the API