Luma: Post V1 Events Ticket Types Create

Create a ticket type for a Luma event, with its capacity, approval setting and sale dates.

Tool ID: luma_post_v1_events_ticket_types_create

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'luma_post_v1_events_ticket_types_create',
  {
    "event_id": "event_123",
    "name": "Example",
    "type": "free"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute luma_post_v1_events_ticket_types_create --input '{
  "event_id": "event_123",
  "name": "Example",
  "type": "free"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "name": "Example",
    "type": "free",
    "id": "id_123"
  }
}

Use deepline describe luma_post_v1_events_ticket_types_create --json for the latest machine-readable contract.

Input reference

Create a new ticket type for an event. Paid ticket types require the calendar to have a connected Stripe account.

Name	Type	Required	Default	Details
`payload.event_id`	`string`	Yes	—	Event ID, this usually starts with evt-
`payload.name`	`string`	Yes	—	Minimum length: 1. Maximum length: 30.
`payload.require_approval`	`boolean`	No	—	—
`payload.is_hidden`	`boolean`	No	—	—
`payload.description`	`string`	No	—	Maximum length: 1000.
`payload.valid_start_at`	`string`	No	—	ISO 8601 Date. For example, 2025-09-01
`payload.valid_end_at`	`string`	No	—	ISO 8601 Date. For example, 2025-09-01
`payload.max_capacity`	`number`	No	—	—
`payload.type`	`"free" \| "paid"`	Yes	—	Allowed: `free`, `paid`.
`payload.cents`	`number`	No	—	—
`payload.currency`	`string`	No	—	—
`payload.is_flexible`	`boolean`	No	—	—
`payload.min_cents`	`number`	No	—	—

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.name`	`string`	Yes	—	Minimum length: 1. Maximum length: 30.
`result.data.require_approval`	`boolean`	No	—	—
`result.data.is_hidden`	`boolean`	No	—	—
`result.data.description`	`string \| null`	No	—	Maximum length: 1000.
`result.data.valid_start_at`	`string \| null`	No	—	ISO 8601 Date. For example, 2025-09-01
`result.data.valid_end_at`	`string \| null`	No	—	ISO 8601 Date. For example, 2025-09-01
`result.data.max_capacity`	`number \| null`	No	—	—
`result.data.type`	`"free" \| "paid"`	Yes	—	Allowed: `free`, `paid`.
`result.data.cents`	`number \| null`	No	—	—
`result.data.currency`	`string \| null`	No	—	—
`result.data.is_flexible`	`boolean`	No	—	—
`result.data.min_cents`	`number \| null`	No	—	—
`result.data.id`	`string`	Yes	—	—
`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.

​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