Proposals
Writes that wait for a person to approve them
A write from the API (scheduling a post, replying to a message) does not run
straight away. It becomes a proposal: the answer says it was queued for
approval and gives its proposalId, and a person approves or rejects it in
Poplitu, in the Inbox. Only then does it run.
That is the default for every connection, so an assistant you connect can draft and prepare but cannot act alone.
Reading and deciding proposals from code
| What | Call |
|---|---|
| List them | GET /api/public/v1/proposals |
| Read one | GET /api/public/v1/proposals/{id} |
| Approve one | POST /api/public/v1/proposals/{id}/approve |
| Reject one | POST /api/public/v1/proposals/{id}/reject |
Approving needs the proposals:approve scope.
Letting writes run without review
A connection that holds mutate:auto runs its writes at once, with no
proposal. Grant it only to code you trust to act on its own: see
Scopes.