> ## 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.

# Inbound Webhook Trigger

> Fire the 'Custom webhook called' scenario trigger from an external system. Any HTTP method is accepted; the request's method, headers, query and body are available to scenario conditions and data injection.

Fire the **Custom webhook called** scenario trigger (`app.scenarios.customTriggers.webhook`) from an external system. Any scenario whose trigger event is *Custom webhook called* runs, with the request's HTTP **method**, **headers**, **query parameters** and **body** available to its conditions and data injection.

**Any HTTP method is accepted** (POST, GET, PUT, ...). The endpoint always responds **200** immediately - scenario execution is asynchronous; use [List Scenario Runs](/api-reference/scenarios-advanced/list-scenario-runs) to inspect what ran.

⚠ **No authentication is performed on this endpoint.** Anyone who knows the URL can fire the trigger. Always send a secret header (e.g. `X-Webhook-Secret`) from your system and add a **condition** in the scenario that checks the header value before any action runs.


## OpenAPI

````yaml api-reference/openapi.json POST /scenarios/webhooks
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).


    ### Using the playground


    On any endpoint page: set **projectID** under *Server* to your project
    subdomain (if your Texter URL is `https://demo.texterchat.com`, the
    projectID is `demo`) and paste your API token into the **Authorization**
    field - both persist while you browse. Create tokens under **gear icon →
    Developers → API Tokens** with the scopes each endpoint lists.
  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/webhooks:
    post:
      tags:
        - Scenarios (Advanced)
      summary: Inbound Webhook Trigger
      description: >-
        Fire the **Custom webhook called** scenario trigger
        (`app.scenarios.customTriggers.webhook`) from an external system. Any
        scenario whose trigger event is *Custom webhook called* runs, with the
        request's HTTP **method**, **headers**, **query parameters** and
        **body** available to its conditions and data injection.


        **Any HTTP method is accepted** (POST, GET, PUT, ...). The endpoint
        always responds **200** immediately - scenario execution is
        asynchronous; use [List Scenario
        Runs](/api-reference/scenarios-advanced/list-scenario-runs) to inspect
        what ran.


        ⚠ **No authentication is performed on this endpoint.** Anyone who knows
        the URL can fire the trigger. Always send a secret header (e.g.
        `X-Webhook-Secret`) from your system and add a **condition** in the
        scenario that checks the header value before any action runs.
      operationId: trigger-scenarios-webhook
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              additionalProperties: true
              description: >-
                Free-form JSON - exposed to scenario conditions and data
                injection
            example:
              event: invoice_paid
              orderId: A-1042
      responses:
        '200':
          description: >-
            Always returned - the trigger was dispatched (whether or not any
            scenario matched)
      security: []
components:
  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.

````