openapi: 3.0.3
info:
  title: Splunk Observability Cloud — Synthetics Chrome flags
  version: 1.0.1
  description: 'API for retrieving a list of Chrome flags supported in Splunk Synthetic Monitoring browser tests.

    Requirements


    You must have an organization access token with the API permission or a session token to use the API.

    You need the Splunk Observability Cloud admin, power, or read_only role to use this API.'
  x-provenance:
    method: reconstructed
    authored_by: Splunk (content) / API Evangelist (assembly)
    reconstructed_by: API Evangelist
    reconstructed_on: '2026-08-19'
    first_party: false
    provider_published: false
    note: Splunk's own OpenAPI objects, extracted from the React Server Component payload embedded in each of the 48 API reference
      pages at dev.splunk.com. The operations and schemas are Splunk's; the assembly into standalone documents is API Evangelist's.
      Splunk serves no fetchable spec file — dev.splunk.com answers 200 with an identical 6,638-byte shell for every asset
      path, including invented control paths — so this is NOT first-party publication and is not graded as such.
  x-evidence:
  - type: source
    url: https://dev.splunk.com/observability/reference/
  - type: source
    url: https://dev.splunk.com/observability/docs/apibasics/api_list/
servers:
- url: https://api.{REALM}.observability.splunkcloud.com/v2/synthetics
  description: Endpoint URL
  variables:
    REALM:
      default: us0
      description: Splunk Observability Cloud realm the organization is provisioned in (for example us0, us1, eu0, jp0, au0).
security:
- SessionToken: []
components:
  securitySchemes:
    SessionToken:
      type: apiKey
      in: header
      name: X-SF-Token
      description: Splunk Observability Cloud session token or org access token.
paths:
  /chrome_flags:
    get:
      summary: syntheticsChromeFlags
      description: 'Returns a list of flags that can be used to customize the browser configuration in Splunk Synthetic Monitoring
        browser tests.

        Requirements


        You must have an organization access token with the API permission or a session token to use the API.

        You need the Splunk Observability Cloud admin, power, or read_only role.'
      parameters:
      - name: X-SF-TOKEN
        in: header
        description: Authentication token
        required: true
        schema:
          type: string
      responses:
        '200':
          description: HTTP 200 response
          content:
            application/json:
              schema:
                type: object
                properties:
                  chromeFlags:
                    type: array
                    items:
                      type: object
                      properties:
                        name:
                          type: string
                          example: --proxy-server
                          description: The name of the flag.
                        acceptsValue:
                          type: boolean
                          example: true
                          description: True if the flag requires a value when set.
                        label:
                          type: string
                          example: Proxy server
                        description:
                          type: string
                          example: Use a specified proxy server.
                          description: A short description of what the flag does.
              examples:
                example:
                  value:
                    chromeFlags:
                    - acceptsValue: true
                      description: Use a specified proxy server.
                      label: Proxy server
                      name: --proxy-server
      security:
      - SessionToken: []
      tags:
      - Synthetics Chrome flags