App Logo
doctolib.fr

List Doctolib appointments

Automatically list Doctolib appointments on doctolib.fr. List the appointments of the signed-in Doctolib account, upcoming or past, as the account's appointments page shows them. Each appointment has its id (the one Cancel Doctolib appointment takes), start and end date, practitioner, speciality, profile path, visit motive, patient, and whether it is confirmed, canceled, past or a no-show. Past appointments come 10 at a time, newest first: pass next_cursor back as cursor for the next ones, until it comes back null. Doctolib removes old appointments from the history after some years. No appointment returns an empty list.

Input

past optional

false: upcoming appointments. true: past appointments, newest first.

Default: false
cursor optional

next_cursor of the previous call with the same past value, to read the next page.

Output

next_cursor required

Pass as cursor for the next page; null on the last page.

appointments required

FAQ

List the appointments of the signed-in Doctolib account, upcoming or past, as the account's appointments page shows them. Each appointment has its id (the one Cancel Doctolib appointment takes), start and end date, practitioner, speciality, profile path, visit motive, patient, and whether it is confirmed, canceled, past or a no-show. Past appointments come 10 at a time, newest first: pass next_cursor back as cursor for the next ones, until it comes back null. Doctolib removes old appointments from the history after some years. No appointment returns an empty list.
Ask an AI agent connected to Reduck to run reduck/doctolib.fr/list_appointments, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/doctolib.fr/list_appointments
You do not need one. "List Doctolib appointments" drives the real doctolib.fr pages in a browser, so it works whether or not doctolib.fr offers an API for this.
Optional: past, cursor.
It returns next_cursor, appointments.
Yes. It acts as you on doctolib.fr: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the doctolib.fr cookies saved by the Reduck extension.
It only reads. It looks things up on doctolib.fr and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/doctolib.fr/list_appointments, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/doctolib.fr/list_appointments
It is part of Reduck's official curated catalogue.

Related scripts

doctolib.fr

Search Doctolib practitioners

Search Doctolib practitioners by specialty and location. Returns total, page, and providers with full_name, specialty, address, sector, payment_means, languages, telehealth, online_booking, matched_visit_motive, and profile_path. There are 20 providers per page and the order is server-ranked; profile_path (including ?pid=practice-N) is the join key for get_practitioner and list_slots.

doctolib.fr

List Doctolib slots

List a Doctolib practitioner's bookable appointment slots for one visit motive over a window of up to 15 days (Doctolib's limit); for a longer span, call again with a later start_date. Returns name, motive, bookable, availabilities (slots by day), total, next_slot (the next slot after an empty window), visit_motives, and booking_url. A motive name that matches several motives, an unknown motive id or an unknown profile fails with a message saying what to pass; pass motive_id to target one motive exactly. booking_url only opens the booking funnel; there is no per-slot link.

doctolib.fr

Get current Doctolib user

Report which Doctolib patient account this browser is signed in as: the account holder's name and email. When the browser is signed out, the run fails with a signed-out error that says to sign in to Doctolib. Same answer as Doctolib whoami.

Start building not clicking

Get started for free