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

> Start a customer verification journey in GBG GO to create a trackable journey instance for an end user.

# Start journey



## OpenAPI

````yaml docs/go-v2/openapi-v2.json POST /journey/start
openapi: 3.0.4
info:
  title: GBG GO API Reference V2
  description: >-
    The GBG GO V2 API enables authentication, customer journey execution, task
    management, and tracking verification progress.
  version: 2.0.0
  license:
    name: MIT
servers:
  - url: https://eu.platform.go.gbgplc.com/v2/captain/
  - url: https://us.platform.go.gbgplc.com/v2/captain/
  - url: https://au.platform.go.gbgplc.com/v2/captain/
  - url: https://api.auth.gbgplc.com/as/token.oauth2
security:
  - bearerAuth: []
paths:
  /journey/start:
    post:
      summary: Start journey
      description: >-
        Start a new journey instance. You can also prefill customer data. For
        more details, see the [start journey
        guide](/docs/go-v2/developer-integration/execute-customer-journeys/start-a-journey-step).
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                resourceId:
                  type: string
                  description: >-
                    Unique identifier for the journey. Append '@latest' to use
                    the most recent version.
                  example: >-
                    97c8b0c5272ba450c48899cc78f6e3f3ba89b5d131c42f7ea972588bd8213b3e@y5z6bj7o
                context:
                  type: object
                  description: Prefilled identity data for the journey.
                  example:
                    config:
                      delivery: page
                    subject: {}
              required:
                - resourceId
      responses:
        '201':
          description: Journey started successfully.
          content:
            application/json:
              schema:
                type: object
                properties:
                  instanceId:
                    type: string
                    description: Unique identifier for the active journey instance.
                  instanceUrl:
                    type: string
                    description: The URL path for the hosted journey page.
                  status:
                    type: string
                    description: Indicates the result of the start request.
                  message:
                    type: string
                    description: Human-readable confirmation message.
              example:
                instanceId: Pq_hhIX6-sHUy9FLSDzPLu
                instanceUrl: /journey/Pq_hhIX6-sHUy9FLSDzPLu
                status: started
                message: Journey Pq_hhIX6-sHUy9FLSDzPLu started successfully
        '404':
          description: >-
            Resource not found. This can happen when using an incorrect endpoint
            URL or an invalid resource ID.
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: integer
                    description: HTTP status code.
                    example: 404
                  message:
                    type: string
                    description: Error message describing what went wrong.
                    example: Not Found Error, validate resource Id
                  error:
                    type: string
                    description: Error identifier for programmatic handling.
                    example: not-found-error
        '405':
          description: >-
            HTTP method not allowed for this endpoint. Make sure your journey
            version is included in the resource Id
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: integer
                    description: HTTP status code.
                    example: 405
                  message:
                    type: string
                    description: Error message explaining the method restriction.
                    example: Method Not Allowed.
                  error:
                    type: string
                    description: Error identifier for programmatic handling.
                    example: method-not-allowed-error
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````