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

# Post organisations board instances trigger execution

> Trigger a board to execute specific start-nodes.




## OpenAPI

````yaml post /organisations/{organisationId}/board-instances/{boardId}/trigger-execution
openapi: 3.0.3
info:
  title: Switchboard API
  description: >-
    The Switchboard API provides users the ability to manage their Apps,
    Integrations and Workflows
  version: 0.0.1-alpha.0
servers:
  - url: https://platform.versori.com/api/switchboard/v1alpha1/
    description: Production server
  - url: http://localhost:8080/v1alpha1/
    description: Localhost
security:
  - apiKey: []
paths:
  /organisations/{organisationId}/board-instances/{boardId}/trigger-execution:
    post:
      tags:
        - boards
      description: |
        Trigger a board to execute specific start-nodes.
      operationId: TriggerBoardExecution
      parameters:
        - name: organisationId
          in: path
          required: true
          schema:
            type: string
          example: '101'
        - name: boardId
          in: path
          required: true
          schema:
            type: string
      requestBody:
        $ref: '#/components/requestBodies/TriggerBoardExecutionRequest'
      responses:
        '202':
          $ref: '#/components/responses/TriggerBoardExecutionResponse'
        default:
          $ref: '#/components/responses/ErrorResponse'
components:
  requestBodies:
    TriggerBoardExecutionRequest:
      description: >
        TriggerBoardExecutionRequest is the payload to trigger a Board to be
        executed
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/TriggerBoardExecution'
  responses:
    TriggerBoardExecutionResponse:
      description: >
        TriggerBoardExecutionResponse is returned after triggering a board to
        execute.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/BoardTriggered'
    ErrorResponse:
      description: The default error response
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    TriggerBoardExecution:
      type: object
      properties:
        nodeIds:
          description: >
            NodeIDs is a list of Node IDs which should be manually triggered. At
            least one ID must be provided.
          type: array
          minItems: 1
          items:
            type: string
      required:
        - nodeIds
    BoardTriggered:
      description: >
        BoardTriggered is used to indicate if the trigger request has been
        accepted. The actual scheduling is

        done in the background and does not indicate the board has finished
        execution yet.
      type: object
      properties:
        ok:
          description: >
            OK denotes whether the request was handled successfully. If this
            field is true, then all nodeIds from the

            request were successfully triggered, otherwise at least one nodeId
            failed to trigger.
          type: boolean
        nodes:
          description: |
            Nodes provides info on which nodes were triggered and if any failed.
          type: array
          minItems: 1
          items:
            $ref: '#/components/schemas/BoardNodeTriggered'
      required:
        - ok
        - nodes
    Error:
      type: object
      properties:
        code:
          type: string
        message:
          type: string
        extensions:
          type: object
      required:
        - code
        - message
    BoardNodeTriggered:
      description: >
        BoardNodeTriggered is used to indicate if the trigger request has been
        accepted for a particular node. Similar

        to BoardTriggered, the actual scheduling is done in the background and
        does not indicate the board has finished

        execution yet.
      type: object
      properties:
        ok:
          description: >
            OK denotes whether the request was handled successfully. If this
            field is true, then the node was triggered,

            otherwise the node failed to trigger.
          type: boolean
        message:
          description: >
            Message contains a human-friendly message to display to the user in
            response to their trigger request.
          type: string
      required:
        - ok
        - message
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: Authorization

````