Probably
Docs

Confirm a spend

confirm_spend, in Spending: A connection or key that may start paid work it prepared.

POST
/api/v1/tools/confirm_spend

Start the paid work a prepare_* or stage tool (research, brainstorm, write_script, review, generate_clip, voice, storyboard) prepared, exactly as its preview showed, once the person has agreed to it. Confirming the same confirmationId again starts nothing more and answers with what it started. Audience research and a campaign's batches and openings run on their Space, not a video, so their videoId is null; research's result names the researchId get_audience_research follows, a batch's its bodies' videos, and openings' each code and run.

Authorization

apiKey
headerAuthorizationBearer <token>

An API key (prb_…) from Settings → Connections.

Request Body

application/json
  1. body
confirmationId*string
Match^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
Formatuuid

Response Body

The tool's answer.

application/json
  1. response
videoId*|null
spaceId*string
Match^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
Formatuuid
result*|||||
curl -X POST 'https://studio.probably.co/api/v1/tools/confirm_spend' \  -H "Authorization: Bearer $PROBABLY_API_KEY" \  -H 'Content-Type: application/json' \  -d '{  "confirmationId": "40b00753-949e-4f8e-a4cc-6b64ed5887e1"}'
{  "videoId": "3524e86f-1bba-489a-bf6b-386ea1abbac0",  "spaceId": "a330a273-e64a-4183-aedb-f3152797a9a5",  "result": {    "kind": "run",    "runId": "78c33d18-170c-44d3-a227-b3194f134f73"  }}