Repurposing API vs raw posting API
PostPeer is a unified posting API: one endpoint that fans a finished post out to every platform. Flowmark is the layer above it. We turn one long-form source into platform-shaped drafts, review them, and feed performance back into the next run.
We are the layer above, not the pipe. Keep your posting plumbing where it is.
Repurposing API vs raw posting API
PostPeer is a unified posting API: one endpoint that fans a finished post out to every platform. Flowmark is the layer above it. We turn one long-form source into platform-shaped drafts, review them, and feed performance back into the next run.
| Feature | Flowmark | PostPeer |
|---|---|---|
| What you send | One long-form source: a blog URL, a transcript or a video description. | A finished post payload you already wrote, plus media. |
| What comes back | Platform-shaped drafts, each with its own voice rules, in one object. | A post id per platform. |
| Content quality | Our problem: per-platform prompt tuning and saved voice presets. | Yours. The API stays neutral on copy. |
| Review | Built-in approval queue, with rejection reasons stacked per platform. | No review layer. Approval happens inside your app. |
| Analytics | Metrics attach back to the source asset and pick the next shape. | Normalised read-only metrics per post id. |
| Video | Transcript-first clip cut points with timestamps and hooks. | Upload or URL ingest with platform media handling. |
| Who it is for | Agencies and SaaS founders shipping a repurposing feature. | Any developer who needs a posting pipe. |
| Relationship | The layer above. Posting plumbing stays where it is. | The plumbing. |
Before you choose
What developers ask about the layer above
What does one call actually return?
One RepurposeJob: the source you sent, a draft per target platform with its own shape, the latency and token cost of the run, and the request and response pair that produced it.
Does this post to the platforms?
No. Posting plumbing stays where it is. Flowmark is the layer above it: the transformation, the review and the feedback. Approved drafts export, and you send them with whatever you already use.
Who owns content quality?
We do. Per-platform prompt tuning and saved voice presets are the product, not a caller responsibility. Reject a draft with a reason and the next run reads it.
What happens to video?
Transcript first. Long-form video becomes ranked clip cut points with timestamps and hooks. There is no rendering or encoding here, by design.
Repurposing as an endpoint, not a roadmap item.
Create an account and a seeded workspace of runs, drafts and metrics is already there.