Webhooks correctly surface the Chili Piper meeting ID when a new meeting is booked, but there is no API endpoint to retrieve meeting IDs for meetings that were booked before a webhook was in place. Customers building automations against the Chili Piper meeting ID have a gap for any historical or pre-existing upcoming meetings.

Customers need an API endpoint that accepts a date range and returns upcoming meetings with their Chili Piper meeting IDs, equivalent to what the webhook payload provides at booking time.

Without this, customers must contact support to have the data pulled manually on the backend, which is not scalable. Teams migrating to webhook-based automations will consistently hit this gap during the transition period.