Luma: Post V1 Events Guests Update Status

Update a guest’s status.

Tool ID: luma_post_v1_events_guests_update_status

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'luma_post_v1_events_guests_update_status',
  {
    "event_id": "event_123",
    "guest_id": "guest_123",
    "status": "approved"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute luma_post_v1_events_guests_update_status --input '{
  "event_id": "event_123",
  "guest_id": "guest_123",
  "status": "approved"
}' --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get luma_post_v1_events_guests_update_status --json for the complete live contract.

Input reference

Update a guest’s status. Set status to approved (“Going”), declined, pending_approval, or waitlist. Use should_refund to refund a paid guest when moving them out of an approved state. Use message to include a personal note in the email we send the guest. To send a soft invite that guests can accept, use /v1/events/guests/send-invites instead.

Name	Type	Required	Default	Details
`payload.event_id`	`string`	Yes	—	Event ID, this usually starts with evt-
`payload.guest_id`	`string`	Yes	—	Guest identifier — the guest ID (gst-), a ticket key, a guest key (g-), or the user’s email.
`payload.status`	`"approved" \| "declined" \| "pending_approval" \| "waitlist"`	Yes	—	Allowed: `approved`, `declined`, `pending_approval`, `waitlist`.
`payload.should_refund`	`boolean`	No	—	If you are moving a guest who has paid to `declined`, `waitlist`, or `pending_approval`, should we refund their payment? Defaults to false.
`payload.send_email`	`boolean`	No	—	Optional. Whether Luma should email the guest about the status change. Defaults to true. Set to false if your integration sends its own notifications.
`payload.message`	`string`	No	—	Optional. Personal message included in the email we send the guest about the status change. Max of 200 characters. Can’t be combined with `send_email: false`. Maximum length: 200.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Empty response
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Luma: Post V1 Events Guests Update Status

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation