Workflows
Run a side-effect-free S16 validation campaign against an exact draft or testing version
POST
/workflow-studio/versions/{uid}/validate
Overview
Quickstart
API reference
Guides
LQM Builder
SDKs
Auth & webhooks
Changes
Versioning
CI
Support
Certification
Programme
Ecosystem
Solutions
References
Evidence exchange
Status
Marketplace
API plans
Contract
Deterministic computations and conditions may execute locally. Waits and artifacts are virtualized. Agent, Integration, Financial Action, code-runner, sub-workflow and external network execution are prohibited.
Authentication
Bearer credential required
Required scope
workflow:manage
Status
Published
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
uid |
path | string | Yes | — |
Code examples
These examples compose a request only. Public reference pages never transmit your credential or execute the operation.
curl
curl -X POST \
-H "Authorization: Bearer $FINANCEGPT_API_KEY" \
-H "Accept: application/json"
"https://financegpt.dev/api/v2/workflow-studio/versions/{uid}/validate"
javascript
const response = await fetch("https:\/\/financegpt.dev\/api\/v2\/workflow-studio\/versions\/{uid}\/validate", {
method: "POST",
headers: {
Authorization: `Bearer ${FINANCEGPT_API_KEY}`,
Accept: 'application/json',
},
});
const data = await response.json();
python
import json
import os
import requests
response = requests.request(
'POST',
'https://financegpt.dev/api/v2/workflow-studio/versions/{uid}/validate',
headers={
'Authorization': 'Bearer ' + os.environ['FINANCEGPT_API_KEY'],
'Accept': 'application/json',
},
)
response.raise_for_status()
print(response.json())
php
<?php
$ch = curl_init('https://financegpt.dev/api/v2/workflow-studio/versions/{uid}/validate');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer '.getenv('FINANCEGPT_API_KEY'),
'Accept: application/json',
],
]);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
Responses
| Status | Description |
|---|---|
202 |
Validation campaign completed with durable evidence |
422 |
Invalid suite |
Authority boundary
A developer credential proves application identity and permits only its scopes. It does not grant model promotion, policy override, QLM rebinding, or Financial Actions execution authority unless those separate controls are satisfied.
workflow:manage