---
title: "Resolve Global Variables Endpoint"
method: GET
path: "/workflows/v1/global-variables/resolve"
tags: ["Global Variables"]
---

# Resolve Global Variables Endpoint

`GET /workflows/v1/global-variables/resolve`

Resolve all global variables for the team into a {name: value} dict.

UI-facing, so every credential is masked — via ``resolve_global_variables_split``, which classifies on
``is_secret`` as well as the system names. The previous ``_mask_system_secrets`` masked only the system
names, so a team's *own* variable marked secret came back in clear from this route. Execution services
use the internal route below.

## Response `200`

Successful Response

- ResolvedGlobalVariablesResponse
  - `variables` object — Resolved {name: value} map, credentials masked
  - `secret_variables` object — Real credential values. Populated ONLY by the internal route, whose sole consumer is conversation_agent_service; empty on the UI-facing route.

## Other responses

- `422` — Validation Error

## Changes

- **2026-08-24** `777675c8a285` — 1 info
  - added the optional property `secret_variables` to the response with the `200` status

[Change history](https://skmtc.dev/interactly/apis/interactly-api-3/changes/workflows/v1/global-variables/resolve/get.md)

---

[API](https://skmtc.dev/interactly/apis/interactly-api-3.md) · [All operations](https://skmtc.dev/interactly/apis/interactly-api-3/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/interactly/interactly-api-3/revisions/35cbea12a781/schema)