documentation

Documentation

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.

How it works

step 1 · POST /v1/connect/:platform

Connect

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.

step 2 · POST /v1/posts

Publish or schedule

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.

step 3 · GET /v1/posts/:id

Know

The production product will report an honest outcome per target account, including whether a retry is appropriate.

The REST contract

These routes exist in the reviewed core, but the public API, account connection, media and webhook flows remain unavailable until their work is reviewed.

POST/v1/posts

Reviewed core route for a repeat-safe publishing job.

GET/v1/posts/:id

Reviewed core route for a job's per-target outcome.

POST/v1/posts/:id/cancel

Planned cancellation before any destination begins.

GET/v1/platforms

Reviewed core route for platform capabilities.

One error language

The planned contract maps platform failures to a canonical error taxonomy, so client code can handle a stable set of cases.

CodeWhat happenedRetryable
auth_revokedYour user disconnected the account, or the platform killed the token. Send them through connect again.false
auth_expiredThe access token aged out. We refresh it and the job runs again on its own.true
rate_limitedThe platform is throttling. We back off and honour retry_after.true
invalid_contentThe post breaks a platform rule: too long, wrong aspect ratio, a link they will not accept.false
media_rejectedThe file failed the platform's own validation. Swap the media and post again.false
platform_errorThe platform returned a 5xx. Their side, not yours. We retry.true
permission_missingYour user never granted the scope this post needs. Ask for it at connect time.false
duplicateThe platform saw this exact post already and refused a second copy. Treat it as published.false

Built for agents

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.

Read the product status