Match posts to scripts now
Match now, the same as the button on the Scripts page: read the transcripts of posts from the last 30 days and of unpaid cycles, score them against the active scripts, and set, keep or flag each one. It runs in the background: this answers 202 at once; follow it with GET /brands/{brandId}/scripts/runs. A match already running answers 202 with alreadyRunning. Without an active script it answers 400. Takes no body.
bearerAuth videos:writeAuthorizationBearer <token>Personal access token. Scopes: account:read, creator:read, creator:earnings, managed:read, coach:read, brand:read, creators:read, videos:read, analytics:read, onboarding:read, onboarding:signatures, engagement:read, support:read, integrations:read, payouts:read, funds:read, billing:read, groups:write, videos:write, onboarding:write, sync:write, payouts:write.
Scope: videos:write
brandId*stringA brand id from GET /me or GET /creator/brands.
1 <= lengthSuccess.
application/json- response
run*alreadyRunning*booleancurl -X POST 'https://example.com/api/v1/brands/string/scripts/match'{ "run": { "id": "string", "trigger": "button", "status": "queued", "queuedAt": "string", "finishedAt": "string", "counts": { "property1": 0, "property2": 0 } }, "alreadyRunning": true}List scripts GET
The brand's scripts: each one's code, title, hooks, body, tag and source, how many posts follow it and how many wait for a pick, plus the brand words and whether matching runs nightly. A post follows a script when matching finds it does; its set then gets the script's tag.
Settle a post's script POST
Answer for a post as a person would in Match history. pick, not_campaign and leave apply to the post's whole set, and no match changes them; the set's tag follows. hand_back undoes that: the set waits for the next match.