Where a posting API stops and an approval layer starts
PostPeer is a unified posting API for developers and AI agents: one endpoint, seven platforms. Approvalrail is the layer above it, for the account manager who has to get a client to say yes first.
| Feature | Approvalrail | PostPeer |
|---|---|---|
| Client sign-off before publish | A hosted review link per post. Release is refused until an approval is on the record. | Not offered as a product surface; you build the screens yourself. |
| Audit trail | Reviewer name, timestamp and note on every state change, kept as immutable rows. | API logs, no human record of who decided what. |
| Who it is for | Agency account managers and the clients who sign off. | Developers and AI agents wiring endpoints. |
| Turning one asset into many posts | Paste a long-form asset and get platform-native drafts in the queue, each linked to the source. | You send finished content, per platform, already written. |
| Queue visibility | One board across every client account, with the approval state on each slot. | Query the scheduling endpoint and render it yourself. |
| Reporting | Approval turnaround, rejection reasons, and who is holding the queue. | Platform metrics and comment endpoints. |
| Setup | Sign in, paste an asset, send a review link. | API key, SDK wiring, and hosting your own interface. |
Put the sign-off on the record.
Create an account and the demo workspace is already in the queue, states and all.