Skip to main content
POST
Create a sub-event

Authorizations

Api-Token
string
header
required

Server-to-server authentication. Generate a token in the admin UI at Settings → Developers → API Access. Send the raw token in the Api-Token header — there is no Bearer prefix.

Tokens can be marked read-only at creation time, in which case the API rejects any non-GET request with 403 Forbidden.

Body

application/json

The new Event resource

name
string
location
string | null
description
string | null
logo
string | null
tags
string | null
parentEvent
unknown
position
integer | null
dateTimeBegin
string<date-time> | null
dateTimeEnd
string<date-time> | null

Response

Event resource created

id
integer
read-only
uuid
string | null
read-only
name
string
location
string | null
description
string | null
logo
string | null
dateCreated
string<date-time>
read-only
tags
string | null
speakers
object[]
parentEvent
unknown
position
integer | null
dateTimeBegin
string<date-time> | null
dateTimeEnd
string<date-time> | null
isPast
boolean
read-only
status
string | null
default:draft