> ## Documentation Index > Fetch the complete documentation index at: https://help.texterchat.com/llms.txt > Use this file to discover all available pages before exploring further. # Create Revision (Publish Draft) > Turn the scenario's current draft into a new revision (a published, activatable version). **Required token scopes:** `Edit scenarios`, `Manage scenarios on behalf of user` (both are required) 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. ## OpenAPI ````yaml he/api-reference/openapi.json POST /scenarios/manage/{scenarioId}/revisions openapi: 3.1.0 info: title: Texter API V2 version: 2.0.0 description: >- The **Texter API** lets your developers control the Texter platform programmatically: - Manage and send your WhatsApp template messages - Retrieve chats by ID or by various filters - Assign and resolve conversations - Send session messages into active chats - Manage labels - Monitor and resolve channel health issues - Subscribe to real-time webhook events - Manage quick replies (coming soon) For any questions please contact [Texter Support](https://wa.me/972586640430). contact: name: Texter Support url: https://wa.me/972586640430 servers: - url: https://{projectID}.texterchat.com/server/api/v2 description: Your Texter environment. Replace projectID with your project subdomain variables: projectID: default: demo description: >- Your unique project subdomain. If your environment URL is https://demo.texterchat.com, your projectID is "demo" security: - bearerAuth: [] tags: - name: Manage Templates description: >- Create, localize, submit, update, delete and send WhatsApp template messages, and retrieve approved templates for your connected WhatsApp accounts. **Suggested token for this group** - create one API token with the scopes: *Send template messages*, *View template messages*, *Manage WhatsApp templates*, *Manage all chats*, *List all chats* (the last two also cover the Templates Subscriptions group). Each endpoint below also lists the exact scopes it needs. - name: Templates Subscriptions description: >- Manage recipient subscriptions for WhatsApp template messages - unsubscribe or resubscribe recipients, and list unsubscribed users across all channels or for a specific account. **Suggested token for this group** - scopes: *Manage all chats*, *List all chats*. Each endpoint below also lists the exact scopes it needs. - name: Messages description: >- Retrieve message history from a chat, or send new session messages - text, media, buttons, lists, contact cards and locations - within the active WhatsApp 24-hour session window. **Suggested token for this group** - scopes: *Send session message*, *View all chats*. Each endpoint below also lists the exact scopes it needs. - name: Chats description: >- Fetch chat details, search conversations, update chat properties, assign or resolve chats, and manage their CRM metadata. **Suggested token for this group** - scopes: *Manage all chats*, *List all chats*, *Send session message*. Each endpoint below also lists the exact scopes it needs. - name: Labels description: >- Create and edit labels, assign or remove them from chats, retrieve label data, or delete labels from your inbox. **Suggested token for this group** - scopes: *Manage labels*, *Manage all chats* (needed for managing labels on chats). Each endpoint below also lists the exact scopes it needs. - name: Channels description: >- Monitor and maintain the health of connected messaging channels - retrieve active channel health problems, filter them by severity or account, and mark issues as resolved. **Suggested token for this group** - scopes: *Manage channels*. Each endpoint below also lists the exact scopes it needs. - name: Quick Replies description: >- Manage quick replies - prepared messages agents can send into matching chats with one click. Quick replies marked with `aiQuickReply` client metadata appear as **AI suggestions** in the Texter inbox (see Create Quick Reply for the full flow). **Suggested token for this group** - scopes: *View quick replies*, *Manage quick replies*. Each endpoint below also lists the exact scopes it needs. - name: Files description: >- Generate public access links to media files stored in Texter. **Suggested token for this group** - scopes: *View all files*, *View all chats* (both required). Each endpoint below also lists the exact scopes it needs. - name: Subscribe to Events description: >- Register webhooks for events occurring in your Texter environment. Under the hood this uses **Scenarios** - a workflow automation feature within Texter. To make integration easy, pre-defined templates are provided: import a scenario JSON, plug in your webhook URL and user UID, and the subscription is active. See the **Webhook Events** pages for the payload your URL receives for each event. **Suggested token for this group** - scopes: *View scenarios*, *Create scenarios*, *Delete scenarios*, *Activate/inactivate scenarios*, *Manage scenarios on behalf of user*. Each endpoint below also lists the exact scopes it needs. If the provided templates don't satisfy your needs, contact [Texter Support](https://wa.me/972586640430) and we'll gladly help modify any triggers, conditions or actions for your webhook. - name: Scenarios (Advanced) description: >- Full programmatic control over scenarios for advanced automations: create scenarios from scratch, copy them, edit drafts, publish revisions, inspect execution runs, and discover the available building blocks (events, conditions, loaders, actions). For plain webhook subscriptions, the **Subscribe to Events** group with its ready-made templates is the simpler path. **Suggested token for this group** - scopes: *View scenarios*, *Create scenarios*, *Edit scenarios*, *Delete scenarios*, *Activate/inactivate scenarios*, *Manage scenarios on behalf of user*, *View scenarios runs*. Each endpoint below also lists the exact scopes it needs. paths: /scenarios/manage/{scenarioId}/revisions: post: tags: - Scenarios (Advanced) summary: Create Revision (Publish Draft) description: >- Turn the scenario's current draft into a new revision (a published, activatable version). **Required token scopes:** `Edit scenarios`, `Manage scenarios on behalf of user` (both are required) 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. operationId: create-scenario-revision parameters: - name: scenarioId in: path required: true schema: type: string description: >- The unique identifier of the subscription (scenario). Use List All Subscriptions to find it under `scenarios[]._id` requestBody: required: false content: application/json: schema: type: object properties: comment: type: string description: Revision comment explaining the changes attachedData: type: object additionalProperties: true description: Free-form data to attach to the revision authorUid: type: string description: Optional - Texter user ID (UID) to attribute the revision to example: comment: Added pending trigger attachedData: deployedBy: ci-pipeline ticket: OPS-142 responses: '201': description: >- The scenario with the new revision. Field-by-field reference: [The Scenario object](/he/api-reference/objects/scenario) content: application/json: schema: $ref: '#/components/schemas/Scenario' '400': description: Validation error or no draft exists content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing or invalid token, or missing required scopes '404': description: Scenario not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: Scenario: type: object description: An event subscription (scenario) in Texter properties: _id: type: string description: Unique identifier of the subscription/scenario system: type: string description: >- System scenario identifier. Present only on built-in system scenarios (returned when `includeSystem=true`) drafts: type: array description: >- 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` items: type: object additionalProperties: true inactiveRevisions: type: array items: $ref: '#/components/schemas/ScenarioRevision' description: Inactive revisions activeRevision: allOf: - $ref: '#/components/schemas/ScenarioRevision' description: The currently active version of the scenario ErrorResponse: type: object properties: error: type: string description: Human-readable error message required: - error ScenarioRevision: type: object description: A specific snapshot of the scenario logic properties: _id: type: string description: Unique identifier of this specific revision scenarioId: type: string description: Reference to the parent scenario ID name: type: string description: Human-readable name of the subscription/scenario description: type: string status: type: string enum: - active - inactive description: The state of this specific revision version: type: number description: The version number of this revision parentVersion: type: number description: The version number this revision was based on revisionComment: type: string triggerEvents: type: array items: type: string description: Internal events that trigger this scenario conditions: type: array description: >- Condition **groups**: an array of groups, each group an array of conditions. All conditions inside a group must pass (AND); the scenario fires if **any** group passes (OR between groups) items: type: array items: type: object properties: name: type: string description: Condition component, e.g. `filtrex`, `compare` params: description: Component parameters confidentialData: type: boolean loaders: type: object description: Data loaders by position properties: beforeConditions: type: array items: type: object properties: name: type: string description: Loader component, e.g. `chat` alias: type: string description: Name under which the loaded data is exposed params: description: Loader parameters confidentialData: type: boolean afterConditions: type: array items: type: object properties: name: type: string description: Loader component, e.g. `chat` alias: type: string description: Name under which the loaded data is exposed params: description: Loader parameters confidentialData: type: boolean actions: type: array description: Actions to execute, e.g. the `request` webhook action items: type: object properties: name: type: string description: Action component, e.g. `request` params: description: Action parameters confidentialData: type: boolean loops: type: array description: Loop definitions, when the scenario iterates over data items: type: object properties: loop: type: object additionalProperties: true description: >- Foreach definition: `input`, `as`, `foreachMode` (`sequential` with `itemDelay`/`breakOnError`, or `parallel` with `concurency`) position: type: string enum: - afterEvents - beforeConditions - afterConditions - beforeActions tags: type: array items: type: string attachedData: type: object additionalProperties: true description: Free-form data attached when the revision was created system: type: string description: >- System scenario identifier. Present only on built-in system scenarios options: type: object properties: unorderedActions: type: boolean description: If true, actions may run in parallel; if false, sequentially metadata: type: object properties: authorUid: type: string description: User ID of the person who created this revision created: type: number description: Timestamp (ms) of revision creation modified: type: number description: Timestamp (ms) of the last draft modification activated: type: number description: Timestamp (ms) of the most recent activation activations: type: array description: History of activations items: type: object properties: timestamp: type: number userUid: type: string securitySchemes: bearerAuth: type: http scheme: bearer description: >- 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. ````