get all bookings filter

[oliverstreuli-stack]

The attendeeEmail query parameter on the GET /v2/bookings endpoint does not filter bookings. It returns all bookings regardless of the specified attendee email.

Create 3 bookings with different attendee emails (e.g., attendee-a@example.com, attendee-b@example.com, attendee-c@example.com)
Call the API with the attendeeEmail filter:
GET https://api.cal.com/v2/bookings?take=100&eventTypeId={your_event_type_id}&attendeeEmail=attendee-a%40example.com
Observe that all 3 bookings are returned instead of only the one matching the filter.
Expected Behavior:

Only bookings where the attendee email exactly matches the filtered email should be returned (1 booking).

Actual Behavior:

All 3 bookings are returned, including those with non-matching attendee emails. The filter is completely ignored.

API Version: v2

Response: The API returns "totalCount": 3 with all bookings, confirming no filtering is applied.

[naaa760]

@oliverstreuli-stack please check it out the PR.

[oliverstreuli-stack]

I reviewed the PR, but I’m still unsure how to properly implement the filter. I’m using Make.

Should I use an Iterator module to filter the bookings? If so, how exactly should I configure the filter to only return the correct attendee email?

Alternatively, is it possible to apply this filtering directly within the HTTP module instead of using an Iterator?

[naaa760]

@oliverstreuli-stack yes filter it at the HTTP/API level (server-side). Don’t use an Iterator.
You can pass attendeeEmail to the Make “List Bookings” request (query param, e.g. ?attendeeEmail=the-attendee@email.com). The endpoint now filters bookings by that attendee email and returns only matching attendees.

[oliverstreuli-stack]

Do you mean filter in the query parameters like displayed in the screenshot? Because it still returns more than one event.

[SahilArate]

Hi, I'd like to work on this bug! 👋
I understand the issue — the attendeeEmail query parameter is being accepted but not actually applied in the filtering logic when fetching bookings. I'll trace the GET /v2/bookings handler to find where the filters are being built and ensure attendeeEmail is properly passed into the database query.
I'll test it by reproducing the exact steps mentioned — creating 3 bookings with different emails and verifying only the matching one is returned after the fix.
Could you please assign this to me?