Scheduling workflow
The Scheduling endpoints let an integrating system find a patient service center (PSC), discover bookable services, list available slots, and create/modify/cancel an appointment for a patient.
Endpoints at a glance
| Step | Endpoint(s) | Tag |
|---|---|---|
| Find a patient service center near a patient | GET /locations/search, GET /locations/{id}, GET /locations | Locations |
| Discover bookable services at a location | GET /services | Services |
| List available appointment slots | GET /appointments/times | Appointments |
| Book an appointment | POST /appointments/v2 | Appointments |
| View/update/cancel an appointment | GET / PUT /appointments/{confirmationNumber}/v2, PUT .../cancel/v2 | Appointments |
| Check an appointment's tracking status | GET /appointments/tracking/{id} | Appointments |
Full schemas and a live "Try it" panel for each endpoint are in the Scheduling API reference.
Typical integration flow
- Search for a location:
GET /locations/search(by address, or by latitude/longitude). - Check available times at that location:
GET /appointments/times. - Book the appointment:
POST /appointments/v2. - Handle the confirmation number in the response.
Authentication
Most Scheduling endpoints (location search, services, appointment times, and appointment creation) are reached through the Labcorp API gateway with a bearer token, the same as every other Labcorp API — see Authentication.
Input validation
Validation is determined by partner type:
| Partner type | Email & address validation |
|---|---|
| Aperture partners (gateway-routed) | Enforced — valid email format and a complete address (line1, city, state, zip) are required |
Direct partners (x-partner-token) | Relaxed — email and address fields may be null, empty, or omitted |
Invalid data returns 400 Bad Request with details in the error body.
De-identified patients
Set deIdentifiedPatient: true on the Patient object for privacy-focused use cases, such as
anonymous screening programs. Some partners are configured to default to de-identified mode when the
flag is omitted, which relaxes certain PII requirements for compliant anonymous data collection.