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

# Create Scenario Studio session

> Creates an interactive scenario creation session for a user.
Returns a URL immediately that the user can visit to complete
scenario creation in the Scenario Studio UI.

The session is pre-populated with the provided prompt, so when the user
opens the URL, the AI agent immediately begins processing their request.




## OpenAPI

````yaml /api-reference/openapi.yaml post /scenario-studio
openapi: 3.0.3
info:
  title: Exec API
  version: '1.0'
  description: >
    REST API for programmatic access to your Exec workspace.


    Use the Exec API to read workspace data, list members, retrieve group
    information,

    and create interactive scenario creation sessions.


    ## Authentication

    All requests require a valid API key passed in the Authorization header:

    ```

    Authorization: Bearer exec_live_...

    ```


    Create API keys in your workspace settings under **Settings > API**.
servers:
  - url: https://api.exec.com/rest/v1
    description: Production
security:
  - bearerAuth: []
paths:
  /scenario-studio:
    post:
      tags:
        - Scenario Studio
      summary: Create Scenario Studio session
      description: |
        Creates an interactive scenario creation session for a user.
        Returns a URL immediately that the user can visit to complete
        scenario creation in the Scenario Studio UI.

        The session is pre-populated with the provided prompt, so when the user
        opens the URL, the AI agent immediately begins processing their request.
      operationId: createScenarioStudioSession
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - user_email
                - prompt
              properties:
                user_email:
                  type: string
                  format: email
                  description: >-
                    Email of the user to create the session for (must be a
                    member of your workspace)
                prompt:
                  type: string
                  description: >-
                    Meeting context or scenario request that will be sent to the
                    AI agent
                request_id:
                  type: string
                  description: >-
                    Optional client-provided ID for deduplication. If provided
                    and a session with this ID already exists, returns the
                    existing session.
            example:
              user_email: jane@acme.com
              prompt: >-
                Create a discovery call scenario for enterprise software sales
                with a skeptical IT director
              request_id: meeting-123-scenario
      responses:
        '200':
          description: Session created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ScenarioStudioSession'
              example:
                id: x9y8z7w6v5u4
                url: https://acme-corp.app.exec.com/chat/x9y8z7w6v5u4
                is_new: true
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    ScenarioStudioSession:
      type: object
      properties:
        id:
          type: string
          description: Session identifier
        url:
          type: string
          format: uri
          description: URL for the user to complete scenario creation
        is_new:
          type: boolean
          description: >-
            True if a new session was created, false if an existing session was
            returned via request_id
    ValidationErrorDetail:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
              description: Error category (e.g., "invalid_request")
            code:
              type: string
              description: Specific error code (e.g., "user_not_found")
            message:
              type: string
              description: Human-readable error message
  responses:
    BadRequest:
      description: Invalid request parameters
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ValidationErrorDetail'
          example:
            error:
              type: invalid_request
              code: invalid_pagination
              message: Invalid pagination parameters
    Unauthorized:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ValidationErrorDetail'
          example:
            error:
              type: authentication_error
              code: invalid_api_key
              message: Invalid or inactive API key
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: |
        API key created in Settings > API.

        Format: `exec_live_` followed by 40 alphanumeric characters.

````