Send a post for client approval
request_approvalThe approval flow: a client reviewer (not a Shager user) gets a link, opens it on their phone without logging in, sees the post per account and approves it or asks for changes (with a comment). The post moves to IN_REVIEW; get_approval shows the decision (APPROVED or CHANGES_REQUESTED); revoke_approval takes the link back while it is pending; an APPROVED post can be scheduled as long as its content is unchanged. An approval requested by an agent never schedules the post by itself, even when it has a date: once get_approval shows APPROVED, call schedule_post. Returns the link to send (and a WhatsApp link when the reviewer has a phone); send_email emails it. When the workspace has approval_required, Shager emails the link to the reviewer itself (reviewer_email and send_email: true are required) and the link is not returned, so the agent can't approve its own post. Useful anyway when a human should look first. (Not available in an unclaimed sandbox.)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workspace_id": "<workspace_id>",
"post_id": "<post_id>",
"reviewer_name": "<reviewer_name>"
},
"name": "request_approval"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | ||
| send_email | No | ||
| workspace_id | Yes | Workspace id from list_workspaces | |
| reviewer_name | Yes | ||
| reviewer_email | No | ||
| reviewer_phone | No | ||
| idempotency_key | No | Any unique string you choose (REST: the Idempotency-Key header works too). Retrying with the same key and body returns the first result instead of creating a second one. Kept 24 hours. |