Multi-step

Scenarios

These create probe records and delete them again when cleanup stays on. Deliveries show up on Webhooks as they arrive.

safe

Read the live contract

Reads the join form, invitations, and events. Nothing is written.

  • The form has exactly one email field.
  • List endpoints return the page envelope.
write

Submit, edit, reject, delete

Creates one invitation with mode submit, edits it while that is allowed, proves retry conflicts, rejects it, and deletes it. If auto-approval is on, submit delivers a platform invite.

  • Email cannot be changed after create.
  • Retry conflicts unless delivery has failed.
  • Reject sets status to rejected.
  • Delete is 204 with an empty body, then the id is not found.
write

Event and applicant lifecycle

Creates an unpublished event, checks idempotency, search, and answer replacement, then deletes the applicant and the event.

  • A new event includes name and email fields.
  • The same idempotency key returns the original applicant, even with a different email.
  • Patch replaces the whole answer object.
  • Deleted records return not found.
deliver

Approve and deliver

Submits an invitation and approves it so Inviter delivers the platform invite. Cleanup removes the invitation record afterward; it does not undo a sent invite.

  • The finished status is sent, delivering, delivery_failed, or approved.
write

Webhook create and delete

Submits one invitation and waits for a verified invitation.created on this browser's webhook URL. Cleanup deletes it and waits for invitation.deleted.

  • The dashboard webhook URL is the session link on the Webhooks page.
  • invitation.created verifies and the read-back matches.
  • invitation.deleted verifies after cleanup.