Skip to main content
Question

POST /invitees returning invalid_location_choice even when event_type.locations matches location_configuration.kind

  • February 16, 2026
  • 1 reply
  • 113 views

I’m attempting to create an invitee via:

POST //api-calendly-com.screenshare.banktechpr.app/invitees

I consistently receive:

{
"title": "Invalid Argument",
"message": "Specified location kind is not configured for this event type.",
"details": [
{
"parameter": "event.location_configuration.kind",
"code": "invalid_location_choice"
}
]
}

Event Type (confirmed via GET)

{
"kind": "solo",
"locations": [
{ "kind": "zoom_conference" }
],
"uri": "//api-calendly-com.screenshare.banktechpr.app/event_types/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
}

Invitee POST body

{
"event_type": "//api-calendly-com.screenshare.banktechpr.app/event_types/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"start_time": "2026-02-17T16:15:00Z",
"invitee": {
"email": "test@example.com",
"name": "Test User",
"timezone": "America/New_York"
},
"location_configuration": {
"kind": "zoom_conference"
}
}

Headers:

  • Content-Type: application/json

  • Authorization: Bearer (PAT)

The event books successfully via the UI, but the API rejects it.

What additional field (if any) is required inside location_configuration for Zoom-based event types?  I’m using POSTMAN to test it.

Thanks in advance.

1 reply

Cameron
Employee
  • Employee
  • May 28, 2026

Hi ​@phillykish  - Thanks for reaching out with your detailed example!

After taking a closer look here, I can confirm that for our POST /invitees endpoint (docs here), the field to send is location, not location_configuration.

For a Zoom event type, you should not need any additional field inside location beyond the kind itself. Your request should look something like this:

{
"event_type": "//api-calendly-com.screenshare.banktechpr.app/event_types/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"start_time": "2026-02-17T16:15:00Z",
"invitee": {
"email": "test@example.com",
"name": "Test User",
"timezone": "America/New_York"
},
"location": {
"kind": "zoom_conference"
}
}

A couple of related notes:

  • location.location is used for location types where a value needs to be supplied, such as physical, custom, ask_invitee, or outbound_call.
  • For zoom_conference, sending just the kind should be sufficient.

So based on what you shared, the most likely cause of the invalid_location_choice error is the request using location_configuration instead of the public API's location field.

If you're already sending location and still seeing the same error, that would be unexpected based on the public API behavior and would be worth reporting to Developer Support by submitting a ticket here with the full raw request and response payload.