Natzar Partner API Reference - v1.0.0
    Preparing search index...

    Interface TelehealthSlot

    One offerable appointment start.

    interface TelehealthSlot {
        startsAt: string;
        endsAt: string;
        localDate: string;
        practitionerIds: string[];
        languages?: string[];
    }
    Index
    startsAt: string

    ISO instant of the start. This is the identity of a slot everywhere.

    endsAt: string

    ISO instant of the consultation's end, WITHOUT the tenant's buffer.

    localDate: string

    Local date in the response's timezone (the timezone you asked for, else the clinic's) — the grouping key for a day grid. Never recompute it from startsAt: a start near midnight files under a different day in a different zone, and this one is already in the zone the grid is drawn in.

    practitionerIds: string[]

    Physicians who published this start and cover the consult's specialty. Pass one back as practitionerId to pin it; omit and the platform picks the least-loaded within the language tier — the patient's language first, then English — which is what you want unless the patient chose a person.

    languages?: string[]

    Every language at least one of those physicians consults in, as base codes in catalogue order (./languages) — so a grid can badge the times that come with a French speaker. Absent when none of them has recorded any. Which of them actually gets the booking is decided at book time (the patient's language first, then English, then least loaded), never by this list.