Skip to main content
POST
Reassign a booked call to a different closer
Swap the host on a booked call. For an upcoming call, under the hood this cancels the existing calendar event and creates a fresh one under the new closer’s calendar, then fires the call.closer_reassigned webhook. For a call that already happened, the swap is attribution-only: the closer columns on the call row are rewritten (so deals, analytics, and commission reads credit the right closer), but no calendar event is created or deleted — the historical event stays on the host who actually held the call. The response and the webhook payload carry attribution_only: true, and the target closer does not need a connected calendar grant. Who can reassign: changing a call’s host is admin only on every surface. An API key keeps access. A signed-in member (a Clerk session) who is not an organization admin gets 403 AUTHORIZATION_ERROR and nothing changes. This applies to a call that already happened, too. Constraints:
  • Call must be in booking kind (intent calls cannot be reassigned)
  • Call must not be cancelled: a cancelled call gets 409 CALL_CANCELLED and nothing changes. Create a new call instead
  • A declined call can be reassigned while its time is still to come: it goes back to waiting for the guest’s answer, and the new closer’s invitation asks the guest again. Once a declined call’s time has passed it cannot be reassigned: it gets 400 VALIDATION_ERROR and nothing changes
  • New closer must be a member of the organization; for upcoming calls they must also have a connected calendar grant
  • Cross-org reassignment is blocked
Side effects visible to Partner API consumers (upcoming calls):
  • DB row’s closer_id / closer_email / closer_name / nylas_event_id / nylas_grant_id / conferencing_link are updated atomically
  • New conferencing link is issued (old one is invalidated)
  • The calendar provider sends the replacement invitation with the guest’s native RSVP controls. Aura also requests withdrawal of the old invitation; if that best-effort delete fails, old_event_orphaned=true reports it
  • call.closer_reassigned webhook fires to all subscribers
  • The recording bot moves to the new meeting link about 20 seconds after the response, or before it for a call that starts within 2 minutes. Until then updated_call.notetaker_id, notetaker_state and meeting_link_sent can still describe the bot that was on the old event
Side effects (past calls, attribution-only):
  • Only closer_id / closer_email / closer_name change; the event id, conferencing link, recording, outcome, and setter attribution stay put
  • call.closer_reassigned webhook fires with attribution_only: true
Sent by Aura for upcoming calls, about 20 seconds after the response:
  • One branded email telling the guest their host has changed (and the new time, when it moved). It carries no calendar file: the replacement invitation above is the calendar update. Partners should not send their own
  • The Zapier event and the call.closer_reassigned Partner webhook, from the same shared reassignment service the dashboard uses

Path Parameters

id
string
required

Call ID (UUID)

Example:

"550e8400-e29b-41d4-a716-446655440000"

Body

application/json
new_closer_id
string
required

Clerk user ID of the closer to reassign the call to (e.g. user_2abc123xyz)

Pattern: ^user_[A-Za-z0-9]+$
Example:

"user_2abc123xyz"

override_conflict
boolean

Deprecated compatibility field. Calendar busy blocks and unverifiable availability always prevent a calendar-changing reassignment, regardless of this value. Past attribution-only reassignment does not change calendars.

Example:

false

Response

Call successfully reassigned

data
object
required
success
enum<boolean>
required
Available options:
true