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

# Container-config get

> Read the tags, triggers and variables of a GTM container, from the published version (`live`) or from a draft workspace.

`live` is what visitors actually execute. A container whose draft holds a perfect setup but was never published tracks nothing, so answer every 'is tracking working' question from `live`.

CLI: `adside google-tag-manager container-config get`



## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/workspaces/{workspaceId}/google-tag-manager/container-config/get
openapi: 3.1.0
info:
  title: Adside API
  version: 1.0.0
  description: >-
    Campaigns, creatives, assets and reporting across your ad accounts. Call it
    with a personal API key as a bearer token, or with the `adside` CLI: each
    page names its command.
servers:
  - url: https://api.adside.ai
    description: Production
security:
  - userAccess: []
tags:
  - name: Account
  - name: Reporting
  - name: Meta
  - name: Google Ads
  - name: LinkedIn
  - name: TikTok
  - name: Reddit
  - name: Snapchat
  - name: X
  - name: Google Tag Manager
  - name: Creatives
  - name: Creative styles
  - name: Media
  - name: Characters
  - name: Assets
  - name: Brands
  - name: Brain
  - name: Research
  - name: Boards
  - name: Artifacts
  - name: Audiences
  - name: Ad comments
  - name: Publications
  - name: Routines
  - name: Skills
  - name: To-dos
  - name: Audit
  - name: Credits
paths:
  /v1/workspaces/{workspaceId}/google-tag-manager/container-config/get:
    post:
      tags:
        - Google Tag Manager
      summary: Container-config get
      description: >-
        Read the tags, triggers and variables of a GTM container, from the
        published version (`live`) or from a draft workspace.


        `live` is what visitors actually execute. A container whose draft holds
        a perfect setup but was never published tracks nothing, so answer every
        'is tracking working' question from `live`.


        CLI: `adside google-tag-manager container-config get`
      operationId: google-tag-manager.get_container_config
      parameters:
        - name: workspaceId
          in: path
          required: true
          schema:
            type: string
            minLength: 1
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $schema: https://json-schema.org/draft/2020-12/schema
              type: object
              properties:
                container_path:
                  type: string
                  description: >-
                    The container's `path`, as returned by `adside
                    google-tag-manager containers list` — e.g.
                    "accounts/6000123/containers/12345678". Not the GTM-XXXXXX
                    public id.
                source:
                  default: live
                  description: >-
                    `live` reads the published version — what visitors actually
                    execute today, and the only thing that reflects reality.
                    `draft` reads a workspace's unpublished changes. Audit
                    questions are always about `live`; `draft` is for checking
                    work that has not been published yet.
                  type: string
                  enum:
                    - live
                    - draft
                workspace_path:
                  description: >-
                    Only with source=draft. The workspace `path` to read.
                    Defaults to the container's Default Workspace when omitted.
                  type: string
              required:
                - container_path
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $schema: https://json-schema.org/draft/2020-12/schema
      security:
        - userAccess: []
components:
  securitySchemes:
    userAccess:
      type: http
      scheme: bearer
      description: >-
        A personal API key (`adside_pat_…`) or a token from `adside login`.
        Either carries the permissions of the person it belongs to.

````

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