/v1/postsReviewed core route for a repeat-safe publishing job.
Booleo is building one REST API and MCP server for publishing now or scheduling one post for later on behalf of your users. The contract is planned; the public API is not available yet.
In a production release, your user will approve on the platform's own consent screen. Booleo will store the token and manage its refresh lifecycle.
The production product will use one request shape for every supported platform. It will publish now or accept one future UTC time, validate a payload before sending it, and permit cancellation before any destination starts.
The production product will report an honest outcome per target account, including whether a retry is appropriate.
These routes exist in the reviewed core, but the public API, account connection, media and webhook flows remain unavailable until their work is reviewed.
/v1/postsReviewed core route for a repeat-safe publishing job.
/v1/posts/:idReviewed core route for a job's per-target outcome.
/v1/posts/:id/cancelPlanned cancellation before any destination begins.
/v1/platformsReviewed core route for platform capabilities.
The planned contract maps platform failures to a canonical error taxonomy, so client code can handle a stable set of cases.
| Code | What happened | Retryable |
|---|---|---|
| auth_revoked | Your user disconnected the account, or the platform killed the token. Send them through connect again. | false |
| auth_expired | The access token aged out. We refresh it and the job runs again on its own. | true |
| rate_limited | The platform is throttling. We back off and honour retry_after. | true |
| invalid_content | The post breaks a platform rule: too long, wrong aspect ratio, a link they will not accept. | false |
| media_rejected | The file failed the platform's own validation. Swap the media and post again. | false |
| platform_error | The platform returned a 5xx. Their side, not yours. We retry. | true |
| permission_missing | Your user never granted the scope this post needs. Ask for it at connect time. | false |
| duplicate | The platform saw this exact post already and refused a second copy. Treat it as published. | false |
The planned hosted MCP server will let an agent act for a specific end user, not one hardcoded account. Before composing, agents will be able to read a capability matrix for each supported platform. Compatibility claims belong here only after the hosted service is available and tested with each named client.