Skip to main content
POST
Typescript (SDK)

Authorizations

Authorization
string
header
required

API key in the format: Bearer {api_token}

Headers

Idempotency-Key
string

Makes this write safe to retry: a repeat with the same key replays the first response instead of creating a second resource. Scoped to the account, remembered for 24 hours; reusing a key with a different payload is an error.

Maximum string length: 255

Body

application/json
type
enum<string>
required

The kind of experience (sellable content/access) to create. Each type builds a different content model managed through its own nested endpoints:

  • course — online course; add modules via POST /experiences/{id}/chapters, lessons via POST /chapters/{id}/lessons
  • digital_download — downloadable files; upload via POST /experiences/{id}/files
  • forum — community; add topics/posts via POST /experiences/{id}/topics and /posts
  • event — live event; add sessions via POST /experiences/{id}/event_sessions
  • event_type — bookable 1:1 session (Cal.com-style); set schedule/form via PATCH details
  • link — link-in-bio; add links via POST /experiences/{id}/link_items
  • written_content — rich-text article (set body via PATCH details)
  • website_embed, discord_server, telegram — embed / external community access Make an experience sellable by linking it to a price variant: POST /price_variants/{id}/experiences.
Available options:
digital_download,
course,
written_content,
website_embed,
link,
forum,
discord_server,
telegram,
event,
event_type
name
string

Display name for the experience

Response

Experience created

id
string
required
object
string
required
name
string
required
slug
string
required
description
string | null
required
access_type
enum<string>
required
Available options:
secret,
open
created_at
string<date-time>
required
updated_at
string<date-time>
required
type
string
required
active_grants_count
integer
required
details
object
required

Type-specific fields, shaped by the experience's type. Mirrors what PATCH accepts under details (see the per-type *DetailsRequest schemas), plus read-only collections (e.g. a course's chapters).