Get all appointments for a community.
Returns a paginated list of booked appointments ordered by appointment ID.
/api/partners/v1/community/:community_id/appointments/booked/Request
Response
No matches returns 404, not an empty list
If nothing matches your filters, this endpoint returns 404 with a data field that's
a descriptive string, not an array — a shape change you need to handle separately from the success case. The
exact wording depends on which date filter you used:
{ "data": "No booked appointments found for provided date: 2024-01-01" }
{ "data": "No booked appointments found in date range: 2024-01-01 to 2024-01-31" }
{ "data": "No booked appointments found" }
The last form appears when neither date nor from_date/to_date was supplied (for example, filtering only by email or phone, or passing no filters at all). Note this differs from an out-of-range page number, which returns a normal 200 with an empty data array instead.
Errors specific to this endpoint
to_date Required (400)
Returned when from_date is supplied without to_date.
from_date Required (400)
Returned when to_date is supplied without from_date.
to_date Before from_date (400)
Returned when to_date is earlier than from_date.
Range Exceeds 365 Days (400)
Returned when the from_date/to_date range spans more than 365 days.
Invalid Phone Number (400)
Returned when phone fails validation. There are three possible message variants depending on why parsing failed: an invalid number ("Invalid phone number."), an unparseable format with additional detail appended ("Could not parse provided phone number: <detail>"), or a bare fallback ("Could not parse provided phone number.") when nothing usable could be extracted.
Invalid page or per_page (400)
Returned when page or per_page isn't a valid integer.