Execute an authorized Financial Action through its separate execution authority
POST
/actions/intents/{uid}/execute
Contract
Execution revalidates current policy and authorization scope. Governed payment, treasury, credit, collection and corporate-action keys additionally require an active execution profile whose action/account/currency/counterparty limits, operating mode, credential boundary, health and kill-switch state pass immediately before dispatch. T3 and T4 actions require explicit human authorization; proposal and observe modes cannot execute. Investment action keys are deliberately rejected here and execute only through the governed investment-order bridge.
actions:execute
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
uid |
path | string | Yes | — |
Code examples
curl
curl -X POST \
-H "Authorization: Bearer $FINANCEGPT_API_KEY" \
-H "Accept: application/json"
"https://financegpt.dev/api/v2/actions/intents/{uid}/execute"
javascript
const response = await fetch("https:\/\/financegpt.dev\/api\/v2\/actions\/intents\/{uid}\/execute", {
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/actions/intents/{uid}/execute',
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/actions/intents/{uid}/execute');
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 |
|---|---|
200 |
Execution evidence and resulting reconciliation state |
422 |
Authorization |
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.
actions:execute