Storyden
Events

Event Participant Remove

Remove a participant from an event. Same rules as EventParticipantUpdate where non-managing members may only remove themselves. Not soft-delete.

Remove a participant from an event. Same rules as EventParticipantUpdate where non-managing members may only remove themselves. Not soft-delete.

DELETE/events/{event_mark}/participants/{account_id}

Authorization

storyden-session<token>

In: cookie

Path Parameters

event_markstring

Either:

  • The unique event ID.
  • The unique event slug.
  • A string of the form -
Formatxid-prefixed-kebab-case-string
account_idstring

Account ID.

Formatxid

Response Body

curl -X DELETE "https://loading/api/events/cc5lnd2s1s4652adtu50-top-10-movies-thread/participants/cc5lnd2s1s4652adtu50"
Empty
Empty
Empty
{
  "error": "string",
  "message": "string",
  "suggested": "string",
  "metadata": {}
}
Edit on GitHub

Event List GET GET

List all events using the filtering options.

Event Participant Update PUT PUT

Add a participant to an event or change an existing participant's state. If the requesting account is an admin or holds MANAGE_EVENTS permission, they can change the participation properties of any account. Otherwise, they can only change their own participation properties. For non-managing members (i.e. not an admin and not a host) this will follow a stricter state machine for the participation status. If the participation status is not set (no participation record is present) or set to "declined", the member may only set their status to "requested" if the event policy is set to "invite_only". Otherwise, they may set it to "attending". If the member is already set to one of these states, they may change it to "declined". A non-managing member cannot change their role and the default is "attendee", only managing members can change participant roles. If the event participation policy is set to "invite_only" then members can only set their status to "requested" or delete their participation. If the event participation policy is set to "closed", it's a no-op. Requests to this resource are idempotent given identical request bodies. It acts as a create-or-update action as participation is account-unique.