> ## Documentation Index
> Fetch the complete documentation index at: https://developers.conveyour.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate a trigger

> Validates a trigger definition without saving it. Returns a success response if the trigger definition is valid, or a list of validation errors if not.

Validate a trigger definition without saving

**Permission:** Requires `automations` **or** `campaigns`; sending `type: "lesson"` additionally requires `lessons`. Denials read `Manage Automations or Campaigns`.

**This does not validate the trigger definition.** Despite the name, the handler builds a preview of which contacts the trigger would affect and returns success regardless — it never runs the model's field validation, so a payload missing required fields still comes back `ok`. Use the create endpoint's response to find validation errors.



## OpenAPI

````yaml /api-reference/specs/triggers.json post /api/triggers/validate
openapi: 3.1.0
info:
  title: ConveYour API — Triggers
  description: Retrieve, create, validate, and update campaign triggers.
  version: 1.0.0
servers:
  - url: https://{subdomain}.conveyour.com
    description: Your organization's ConveYour instance
    variables:
      subdomain:
        default: acme
        description: >-
          Your organization's slug — the subdomain you sign in on. Replace
          `acme` with yours: if you sign in at `bigco.conveyour.com`, enter
          `bigco`.
security:
  - conveyourToken: []
tags:
  - name: Triggers
    description: Retrieve, create, validate, and update campaign triggers.
paths:
  /api/triggers/validate:
    post:
      tags:
        - Triggers
      summary: Validate a trigger
      description: >-
        Validates a trigger definition without saving it. Returns a success
        response if the trigger definition is valid, or a list of validation
        errors if not.


        Validate a trigger definition without saving


        **Permission:** Requires `automations` **or** `campaigns`; sending
        `type: "lesson"` additionally requires `lessons`. Denials read `Manage
        Automations or Campaigns`.


        **This does not validate the trigger definition.** Despite the name, the
        handler builds a preview of which contacts the trigger would affect and
        returns success regardless — it never runs the model's field validation,
        so a payload missing required fields still comes back `ok`. Use the
        create endpoint's response to find validation errors.
      operationId: validateATriggerDefinitionWithoutSaving
      parameters:
        - $ref: '#/components/parameters/teams'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - type
              properties:
                type:
                  description: The trigger type to validate.
                  type: string
                campaign_id:
                  description: Campaign context for validation.
                  type: string
                ...:
                  description: >-
                    Type-specific fields at the top level (same as POST
                    /api/triggers). No `config` wrapper.
                  type: string
      responses:
        '200':
          description: Success.
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Envelope'
                  - type: object
                    properties:
                      data:
                        $ref: '#/components/schemas/TriggerValidation'
              example:
                status: ok
                message: success
        '403':
          $ref: '#/components/responses/Forbidden'
components:
  parameters:
    teams:
      name: teams[]
      in: query
      description: >-
        Team scope for the request, as one or more team ObjectIds. The brackets
        are required: PHP keeps only the last value for a repeated plain key, so
        `teams=A&teams=B` silently resolves to B alone. On requests with a JSON
        body you may send `teams` (no brackets) in the body instead.


        **Values that are not valid ObjectIds are silently ignored** — a
        mistyped team ID behaves as if no team was sent. See the [teams section
        of the API conventions guide](/guides/api-conventions#team-scoping).
      style: form
      explode: true
      schema:
        type: array
        items:
          type: string
      example:
        - 64a1b2c3d4e5f6a7b8c9d0ff
  schemas:
    Envelope:
      type: object
      description: The common response envelope shared by all ConveYour endpoints.
      properties:
        status:
          type: string
          enum:
            - ok
            - failed
          description: '`ok` on success, `failed` on error.'
        message:
          type: string
          description: Human-readable description of the result.
        data:
          description: >-
            The response payload — an object or an array depending on the
            endpoint.
    TriggerValidation:
      type: object
      description: >-
        Whatever the trigger type's validation returns for the submitted
        payload. It is not a trigger record, and its keys vary by trigger type —
        a falsy result is returned as an error instead.
  responses:
    Forbidden:
      description: >-
        The token is missing or invalid, or the service account behind it lacks
        the permission this endpoint requires.
      content:
        application/json:
          example:
            status: failed
            message: Lacking necessary permission add_contacts
            data:
              permission: add_contacts
  securitySchemes:
    conveyourToken:
      type: apiKey
      in: header
      name: x-conveyour-token
      description: >-
        Your API key token. Contacts endpoints require a **Server-only — Full
        API** key — see [Authentication](/quickstart).

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.