Skip to main content
PATCH
Update Draft
Required token scopes: Edit scenarios, Manage scenarios on behalf of user (both are required) Use the List Components endpoints to discover valid event, loader, condition and action names and their parameters. Optionally, you can include an authorUid body field (a Texter user UID) to attribute the action to a specific user; when omitted, it is attributed automatically.

Authorizations

Authorization
string
header
required

API token generated in Texter: gear icon → Developers → API Tokens. When creating a token, assign it the scopes required by the endpoints you plan to call - each endpoint lists its required scopes.

Path Parameters

scenarioId
string
required

The unique identifier of the subscription (scenario). Use List All Subscriptions to find it under scenarios[]._id

Body

application/json
Minimum array length: 1

Response

The scenario with the updated draft. Field-by-field reference: The Scenario object

An event subscription (scenario) in Texter

_id
string

Unique identifier of the subscription/scenario

system
string

System scenario identifier. Present only on built-in system scenarios (returned when includeSystem=true)

drafts
object[]

Draft revisions of this scenario being edited. Same shape as a revision, but with status: "draft", no version/revisionComment, and metadata limited to authorUid/created/modified

inactiveRevisions
object[]

Inactive revisions

activeRevision
object

The currently active version of the scenario