we wanna have the following endpoints for api v2:
- https://cal.com/docs/api-reference/v1/attendees/find-all-attendees
- https://cal.com/docs/api-reference/v1/attendees/find-an-attendee
think we can reuse the existing logic that v2 has, this shouldn't require any extra logic
Note: we need to make sure we add more aggressive rate limiting on these endpoints. the attendees table is super massive so anyone starts spamming this and we'll be in trouble
we wanna have the following endpoints for api v2:
think we can reuse the existing logic that v2 has, this shouldn't require any extra logic
Note: we need to make sure we add more aggressive rate limiting on these endpoints. the attendees table is super massive so anyone starts spamming this and we'll be in trouble