Static scheduling links can't be scoped to a specific campaign or capped by use count. Teams sharing links in outbound sequences have no way to track which campaign drove a booking, and nothing prevents a prospect from reusing a link outside the intended window.

A POST endpoint should allow developers to programmatically generate unique booking URLs with a configurable max_event_count and a specified owner or Meeting Type. Once the limit is reached, the link expires.

This is a direct Calendly parity gap. Teams currently work around it with UTM parameters, which are unreliable, or avoid dynamic link generation entirely.