Skyvern: List tag values
Skyvern tags.listTagValues: arguments, response, policy and SDK examples.
← Tags operations · Get started
Operation skyvern.list_tag_values_v1_tag_values_get
Provider route: GET /v1/tag-values. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/skyvern with npm, or alter-sdk-skyvern with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { SkyvernIntegration } from "@alter-ai/skyvern";
async function execute(input: Parameters<SkyvernIntegration["tags"]["listTagValues"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new SkyvernIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.tags.listTagValues(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_skyvern import SkyvernIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = SkyvernIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.tags.list_tag_values(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
query | object | Optional | Additional keys: not allowed |
query.key | JSON | Optional | Filter to values for a single tag key |
query.key (anyOf 1) | string | Alternative | |
query.key (anyOf 2) | null | Alternative |
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | array | Root | |
$[] | Model | Each item | Expand Create tag value — response body |
Referenced models: Create tag value — response body
Schemas
Section titled “Schemas”Create tag value — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Tag-value color registry entry: the palette color assigned to a grouped (key, value) pair. |
color | string | Required within parent | |
key | string | Required within parent | |
value | string | Required within parent | |
workflow_count | JSON | Optional | |
workflow_count (anyOf 1) | integer | Alternative | Number of non-deleted workflows currently carrying this (key, value) label. Default: 0 |
workflow_count (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: skyvern.list_tag_values_v1_tag_values_get. Catalog operation: list_tag_values_v1_tag_values_get. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.