Booking meetings

One request books a meeting. Rescheduling and cancelling are one request each, and every guest is kept informed.

Create

POST /meetings needs the customer (tenantRef), a title, at least one invitee and an idempotencyKey. Optional: scheduledAt (leave it out to let the guest choose), durationMinutes (30 by default), identityAddress (the customer's default address if left out) and consumerMeetingRef, your own reference, which Aura keeps for you.

Exactly once, every time

Networks drop. If your app retries a booking with the same idempotencyKey, Aura returns the meeting it already made instead of booking a second one. Use a key that belongs to the booking in your system, such as its id.

Reschedule and cancel

POST /meetings/{externalId}/reschedule   { "scheduledAt": "…", "idempotencyKey": "…" }
POST /meetings/{externalId}/cancel       { "reason": "…", "idempotencyKey": "…" }

Both are safe to retry in the same way. A meeting that has ended or been cancelled can't be changed, and Aura says so clearly.

Meeting status