Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
application/json Body
The event description in Slack message content format.
- Option 1
- Option 2
{ "text": "This is the event description." }{
"blocks": [
{
"type": "rich_text",
"elements": [
{
"type": "rich_text_section",
"elements": [
{
"text": "This is the event description.",
"type": "text"
}
]
}
]
}
]
}An ISO 8601 date and time, with optional timezone offset
"2025-01-07T15:00:00-07:00"
An ISO 8601 date and time, with optional timezone offset
"2025-01-07T15:00:00-07:00"
3 - 70"My Event"
The Slack channel(s) that the event announcements are posted to when published.
1 - 10 elements"John Doe, Jane Doe"
"https://example.com/my-event"
"1 Market Street, San Francisco, CA"
"https://lu.ma/event/evt-6pGPLeDBObis0G4"
The event recap in Slack message content format.
{ "text": "This is the event recap." }{
"blocks": [
{
"type": "rich_text",
"elements": [
{
"type": "rich_text_section",
"elements": [
{
"text": "This is the event recap.",
"type": "text"
}
]
}
]
}
]
}"https://www.youtube.com/watch?v=abc123"
"third-party-event-id"
The URL slug for the event. If not provided, one will be generated based off the title.
3 - 70"my-event"
The event status. Events created with "published" status will immediately be published to the specified Slack channel(s) and possibly to the site. Events created with "needs_approval" status will be submitted for admin approval. Events cannot be created with "draft" status from the API.
needs_approval, published "published"
The user(s) featured as a host for the event, which must be one of the following: Slack user IDs, emails, or Tightknit profile IDs
The user(s) featured as a speaker for the event, which must be one of the following: Slack user IDs, emails, or Tightknit profile IDs
The id of the File to use as the cover image for the event
"97d5c5d6-d036-4223-9bd3-876a0cf47751"

