Org Content

Answer an event invitation

PUT/org-content/event/{event_id}/rsvp
org-content:engagereplace_org_event_rsvpDestructiveIdempotent

Sets the acting user's answer to the event and returns it as the GET does. It always acts as the token's user: user_id, author or author_id returns 422 missing. Emits event_rsvp.updated on every call, even when the answer is unchanged; no email or notification. Sending the earlier status undoes it. dry_run shows the result without saving it.

Path parameters

  • event_idstring (uuid)Required#

    The event's id.

Query parameters

  • dry_runboolean#

    Validate and run the call without committing it, returning what the real call would return with meta.dry_run set.

Request body

application/json, required · OrgEventRsvpUpdate

  • statusstringRequired#

    The answer: going, maybe or declined.

    One of: going, maybe, declined
{
  "status": "going"
}

Responses

200

The acting user's answer as set.

OrgEventRsvpEnvelope
{
  "data": {
    "status": "going",
    "counts": null,
    "can_see_responses": false
  }
}
401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error
403

Authorization failed. error.code is one of org_disabled, ip_blocked, missing_scope, scope_disabled, user_disabled.

Error
404

Resource not found (error.code = not_found).

Error
409

The request conflicts with existing state (error.code = conflict), e.g. a compliance flow with the requested name already exists.

Error
422

The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per problem, or a code documented on the operation.

Error
429

Rate limit exceeded (error.code = rate_limited).

Error

Examples

curl -X PUT https://your-org-domain/kong/core/api/v2/org-content/event/{event_id}/rsvp\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"\
  -d '{
  "status": "going"
}'