Create experience (course, digital download, forum, event, link, etc.)
Creates an experience of the given type — the entry point for selling a course, community/forum, live event, digital download, bookable session, or link-in-bio. Each type builds its own type-specific item with its own nested content endpoints (e.g. a course gets chapters → lessons; a forum gets topics/posts; an event gets sessions). A new experience starts empty — add content via the nested endpoints, set type-specific fields with PATCH /experiences/ via details, and make it sellable by linking it to a price variant with POST /price_variants//experiences. See the type field for the full list and per-type content model.
Authorizations
API key in the format: Bearer {api_token}
Headers
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.
255Body
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}/lessonsdigital_download— downloadable files; upload via POST /experiences/{id}/filesforum— community; add topics/posts via POST /experiences/{id}/topics and /postsevent— live event; add sessions via POST /experiences/{id}/event_sessionsevent_type— bookable 1:1 session (Cal.com-style); set schedule/form via PATCH detailslink— link-in-bio; add links via POST /experiences/{id}/link_itemswritten_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.
digital_download, course, written_content, website_embed, link, forum, discord_server, telegram, event, event_type Display name for the experience
Response
Experience created
secret, open 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).

