Check that the Tag Manager client is configured and can authenticate.

Returns: Whether credentials resolve, whether the server is in read-only mode, and the OAuth scopes in use.

List the Google Tag Manager accounts this user can access.

Start here: every other tool needs an account ID, and the numbers shown in the Tag Manager web UI's URL are not always the API's account IDs.

Get one Tag Manager account.

Update a Tag Manager account's settings.

List who has access to a Tag Manager account, and at what level.

Get one user's access to a Tag Manager account.

Grant a user access to a Tag Manager account.

Change a user's access to a Tag Manager account.

The request replaces the stored access levels rather than merging into them, so send the complete accountAccess and containerAccess you want.

Revoke a user's access to a Tag Manager account.

List the containers in a Tag Manager account.

Get one Tag Manager container.

Find a container from its public GTM-XXXXXXX tag ID.

Use this when you have a tag ID from a website's source but no account ID. Pass exactly one of the two arguments.

Get the HTML install snippet for a container.

Create a container in a Tag Manager account.

Update a container's settings.

Delete a container, and with it every workspace, tag and version.

This cannot be undone through the API, and any site still loading the container's snippet stops receiving tags.

Merge one container into another.

Move a tag ID out of a container into a newly created one.

The inverse of combine_containers: it splits a tag ID off a container that holds several.

List the Google tag destinations linked to a container.

Get one destination linked to a container.

Link a Google tag destination to a container.

The destination is taken from whichever container currently holds it, so this moves rather than copies.

List a container's environments.

Every container has a Live and a Latest environment; the rest are user-created preview targets.

Get one container environment.

Create an environment in a container.

Update a container environment.

Delete a container environment.

The built-in Live and Latest environments cannot be deleted.

Regenerate an environment's authorization code.

Use this when a preview link has leaked: the old code stops working immediately, so anything embedding it must be updated.

List a container's version history as lightweight headers.

Prefer this over fetching versions when you want the history: a header carries the ID, name and entity counts without the full snapshot of every tag in the version.

Get the header of a container's most recently created version.

This is the newest version, which is not necessarily the published one -- use get_live_version for what production is serving.

Get one container version, including every entity it contains.

Get the container version currently published to production.

This is what visitors to the site are actually running, which is the right starting point for "what is live right now".

Update a container version's name or notes.

Only the metadata is editable. A version's entities are a frozen snapshot; to change them, edit a workspace and create a new version.

Delete a container version.

Deletion is reversible with undelete_version. The live version cannot be deleted.

Restore a deleted container version.

Publish a container version to production.

This takes effect on the live site immediately, for every visitor, with no staged rollout. The only way back is to publish an earlier version over the top. Confirm the version is the intended one before calling.

Set the version that workspaces sync against.

This is the baseline used to detect conflicts when a workspace syncs. It does not change what is published.

List a container's workspaces.

A workspace is the draft layer: tags, triggers and variables are edited in one, and nothing reaches production until it becomes a version and that version is published. Every container has a "Default Workspace".

Get one workspace.

List what a workspace has changed, and what conflicts with the base.

Run this before creating a version: it is the diff between the workspace and the container version it was branched from.

Create a workspace in a container.

Update a workspace's name or description.

Delete a workspace, discarding every change in it.

Changes that were never turned into a version are lost. Check get_workspace_status first.

Bring a workspace up to date with the latest container version.

Unmodified entities are updated in place; anything the workspace also changed comes back as a merge conflict to resolve with resolve_workspace_conflict.

Resolve one merge conflict raised by sync_workspace.

Compile a workspace into a throwaway version to check it is valid.

Nothing is saved and nothing is published; this is the cheap way to find compiler errors before create_version.

Turn a workspace into a container version.

The workspace is consumed by this call -- the API deletes it and makes the new version the container's latest. Creating a version does not publish it; use publish_version for that.

Apply many entity changes to a workspace in a single call.

Use this when creating entities that reference each other -- a tag and the trigger that fires it, say -- since one call keeps them consistent.

List the tags in a workspace.

Get one tag from a workspace.

Create a tag in a workspace.

Update a tag in a workspace.

The tag you send replaces the stored one, so read it with get_tag first and send the whole thing back with your edits applied. Omitted fields are cleared, not preserved.

Delete a tag from a workspace.

This affects the workspace only. The tag keeps running in production until a version without it is published.

Undo a workspace's changes to one tag.

Restores the tag to the state of the container version the workspace was branched from, leaving the workspace's other changes alone.

List the triggers in a workspace.

Triggers are referenced by tags through firingTriggerId and blockingTriggerId, so list these before creating a tag.

Get one trigger from a workspace.

Create a trigger in a workspace.

Trigger types are Tag Manager's internal codes: "pageview", "domReady", "windowLoaded", "click", "linkClick", "formSubmission", "customEvent", "timer" and so on. Copy the shape from an existing trigger via get_trigger when unsure.

Update a trigger in a workspace.

The trigger you send replaces the stored one, so read it with get_trigger first and send the whole thing back with your edits applied. Omitted fields are cleared, not preserved.

Delete a trigger from a workspace.

This affects the workspace only. The trigger stays in production until a version without it is published.

Undo a workspace's changes to one trigger.

Restores the trigger to the state of the container version the workspace was branched from, leaving the workspace's other changes alone.

List the variables in a workspace.

Other entities reference these by name in {{double braces}}, so the names here are what tag and trigger parameters point at.

Get one variable from a workspace.

Create a variable in a workspace.

Variable types are Tag Manager's internal codes: "v" is a data layer variable, "c" a constant, "jsm" custom JavaScript, "k" a first-party cookie, "u" a URL variable. Copy the shape from an existing variable via get_variable when unsure.

Update a variable in a workspace.

The variable you send replaces the stored one, so read it with get_variable first and send the whole thing back with your edits applied. Omitted fields are cleared, not preserved.

Delete a variable from a workspace.

This affects the workspace only. The variable stays in production until a version without it is published.

Undo a workspace's changes to one variable.

Restores the variable to the state of the container version the workspace was branched from, leaving the workspace's other changes alone.

List the built-in variables enabled in a workspace.

Built-in variables (Page URL, Click Text, and so on) are supplied by Tag Manager and only need enabling. They are separate from the user-defined variables in list_variables.

Enable built-in variables in a workspace.

Disable built-in variables in a workspace.

Anything referencing a disabled variable stops resolving, so check for uses first.

Undo a workspace's change to one built-in variable.

List the folders in a workspace.

Get one folder from a workspace.

List the tags, triggers and variables inside a folder.

Create a folder in a workspace.

Update a folder's name or notes.

Delete a folder from a workspace.

The entities inside it are not deleted; they are left unfiled.

Undo a workspace's changes to one folder.

Move tags, triggers and variables into a folder.

Pass folder_id "0" to take the entities out of their current folder instead of putting them into one.

List the custom templates in a workspace.

Get one custom template, including its sandboxed JavaScript source.

Create a custom template in a workspace.

Update a custom template in a workspace.

The template you send replaces the stored one, so read it with get_template first and send the whole thing back with your edits applied.

Delete a custom template from a workspace.

Tags and variables using the template stop working, so check for uses before deleting.

Undo a workspace's changes to one custom template.

Import a template from the Community Template Gallery.

Gallery templates are third-party code that runs on the site, and the import declares the permissions the template asks for -- acknowledge_permissions must be true or the call fails. Review what it requests before importing.

List the clients in a workspace.

A web container returns an empty list; clients exist only in server containers.

Get one client from a workspace.

Create a client in a workspace.

Only server containers accept clients. Creating one in a web container fails.

Update a client in a workspace.

The client you send replaces the stored one, so read it with get_client first and send the whole thing back with your edits applied. Omitted fields are cleared, not preserved.

Delete a client from a workspace.

This affects the workspace only. The client stays in production until a version without it is published.

Undo a workspace's changes to one client.

Restores the client to the state of the container version the workspace was branched from, leaving the workspace's other changes alone.

List the transformations in a workspace.

A web container returns an empty list; transformations exist only in server containers.

Get one transformation from a workspace.

Create a transformation in a workspace.

Only server containers accept transformations. Creating one in a web container fails.

Update a transformation in a workspace.

The transformation you send replaces the stored one, so read it with get_transformation first and send the whole thing back with your edits applied. Omitted fields are cleared, not preserved.

Delete a transformation from a workspace.

This affects the workspace only. The transformation stays in production until a version without it is published.

Undo a workspace's changes to one transformation.

Restores the transformation to the state of the container version the workspace was branched from, leaving the workspace's other changes alone.

List the zones in a workspace.

A standard (non-360) container returns an empty list.

Get one zone from a workspace.

Create a zone in a workspace.

Zones require Tag Manager 360. Creating one in a standard container fails.

Update a zone in a workspace.

The zone you send replaces the stored one, so read it with get_zone first and send the whole thing back with your edits applied. Omitted fields are cleared, not preserved.

Delete a zone from a workspace.

This affects the workspace only. The zone stays in production until a version without it is published.

Undo a workspace's changes to one zone.

Restores the zone to the state of the container version the workspace was branched from, leaving the workspace's other changes alone.

List the Google tag configurations in a workspace.

These are the gtag.js settings a Google tag applies to its destinations -- the API equivalent of the "Configuration settings" panel on a Google tag.

Get one Google tag configuration from a workspace.

Create a Google tag configuration in a workspace.

Update a Google tag configuration.

The config you send replaces the stored one, so read it with get_gtag_config first and send the whole thing back with your edits applied.

Delete a Google tag configuration from a workspace.

Unlike every other workspace entity, Google tag configs have no revert method, so this cannot be undone short of discarding the workspace.

Read everything configured in a workspace in one call.

Fetches tags, triggers, variables and folders, following pagination on each. Prefer this over four separate list calls when you want to understand or audit a container's setup.

Find tags, triggers and variables by name.

The API has no search, so this reads each collection and filters. Use it to turn a name a human used ("the purchase tag") into the ID the other tools need.

Summarise a container: settings, workspaces and what is live.

The quickest answer to "what is this container and what is it running".

List every container this user can reach, across every account.

Answers "what do I have access to" in one call instead of one list_containers per account. An account that cannot be read is reported with its error rather than failing the whole call.

Create a container version from a workspace, optionally publishing it.

This is the Tag Manager release flow: a workspace becomes a version, and a version is published. Creating the version consumes the workspace either way.

publish defaults to false. Passing true releases to the live site immediately, for every visitor -- confirm that is intended before setting it. A version that fails to compile is never published.