v1Resources/Approvals/postApprove an item

Approve an item

Approves a pending item and runs it. For held content you can approve it anyway after reviewing its content checks, give it a new send time, or record a reason. Answers 409 when it was already decided, and 502 when it was approved but the action failed.

post/api/v1/approvals/{id}/approve
approvals:write
Query parameters
idstringrequired
Request body
reasonstringoptional
Why you approved or declined it, up to 2,000 characters. It is kept with the decision.
scheduledForstringoptional
A new time to publish content at, as a date-time. Leave it out to keep the time the item already has.
anywayobjectoptional
Approve content even though its content checks flagged it: send the fingerprint of the check result you reviewed and the keys of the findings you accept.
fingerprintstringoptional
acceptedKeysarray of stringoptional
Response
dataobjectoptional
idstringoptional
statusstring (pending | approved | rejected)optional
kindstringoptional
What kind of item this is, for example content your agent drafted or an action held by your autonomy rules.
originstringoptional
titlestringoptional
summarystringoptional
clientIdstringoptional
modulestringoptional
changeobjectoptional
The exact action that runs on approval: the tool, its arguments and the fields it changes.
toolstringoptional
argsobjectoptional
fieldsarray of objectoptional
contentobjectoptional
The drafted content, when the item is content.
requestedAtstringoptional
scheduledForstringoptional
expiresAtstringoptional
decidedAtstringoptional
decidedBystringoptional
Who made the decision, or null while it is still pending.
decisionReasonstringoptional
publishStatestring (published | failed)optional
publishErrorstringoptional
publishedAtstringoptional
Errors
401Missing, invalid, expired, or revoked API key.
403The key lacks the required scope, or isn't authorized for this client/location.
404The resource wasn't found, or doesn't belong to your agency.
409The request conflicts with the current state of the resource — for example, changing the email or phone of a recipient who has already been messaged, or a team invite that was already accepted (or hasn't been accepted yet).
429Too many requests. Retry after the number of seconds in the Retry-After header.
502The item was approved but the action failed to run. The error says why.
post/api/v1/approvals/{id}/approve
Your API key
id *
Request body
{}

New to the Synup API?