是否要立即開始使用？閱讀開發人員指南。每個使用該 API 的應用程式都必須完成幾個步驟，才能註冊、授權使用者，以及使用 API。開發人員指南將引導您逐步完成每個步驟，最後也會提供可自訂的有效應用程式。
概念總覽
這個 API 會公開階層式的多個 Google 代碼管理工具設定實體。每位使用者的帳戶可以有一或多個容器，每個容器可包含一或多個工作區。工作區可對容器的變數、內建變數、觸發條件、資料夾和標記進行多項並行修改。對工作區進行所需的修改後，您可以建立、預覽及發布版本。您可以運用權限資源在帳戶層級管理使用者權限。下圖代表實體之間的父項與子項關係：
圖 1：Google 代碼管理工具資源的父項-子項關係。
Google 代碼管理工具 API 會將每個實體顯示為資源。特定種類的資源清單，構成了集合。API 會在 URI 中公開每個集合，可供查詢以傳回當中的實體清單。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2024-05-01 (世界標準時間)。"],[[["The Google Tag Manager API grants authorized users access to Google Tag Manager configuration data, allowing management of accounts, containers, workspaces, tags, triggers, and other related entities."],["Before using the API, developers need to register their application, authorize the user, and understand the workflow as detailed in the Developer's Guide."],["Google Tag Manager resources are organized hierarchically, with accounts containing containers, containers containing workspaces, and workspaces containing various elements like tags, triggers, and variables."],["The API utilizes a quota system to ensure equitable resource distribution and protect the system from overload, with specific limits outlined in the Limits and Quotas guide."],["Further information and guidance on working with the API can be found in the Developer's Guide and the Tag Manager API Reference."]]],[]]
