How It Works

Whether the request comes from the composer, the API, an SDK, or the agent, the path is the same.

You  →  FoPost  →  30 networks

The vocabulary

Account. One connected profile on one network. A workspace can hold several on the same network, so posts target accounts, not network names.

Post. Content plus the accounts it targets. One post, many destinations.

Delivery. One post reaching one account. Deliveries succeed and fail independently, which is why a post can be partially failed.

Workspace. The boundary everything lives inside. Accounts, posts, media, analytics, and team. Nothing crosses.

Publishing

1. You create a post and pick the accounts
2. Preflight checks it against each network: content over a limit, a media type that will be refused, a missing required field. Blockers stop it here, where a fix costs nothing
3. Each account is queued as its own delivery
4. Each network is called with content formatted for it and media resized for it
5. Results come back per account, with a link to the live item, or a reason it failed
6. You hear about it in the dashboard, or through a webhook

Deliveries are independent throughout. One network being down does not hold up the other four.

Scheduling

A scheduled post sits until its time, then enters the same pipeline. It runs on our servers, so nothing depends on your browser.

If the queue loses its connection, orphaned deliveries are recovered and re-queued rather than silently dropped.

Retries

Transient failures are retried automatically with a growing gap. A rate limit or a brief outage recovers without you.

Permanent failures are not retried, because they would fail identically forever: an expired token, content over the limit, a rejected media type. Those wait for you, with the reason stated.

Formatting

Per network, and automatic:

• Character limits, cut on a word boundary
• Threads where the network supports them
• Markup converted to whatever that network parses
• Hashtags placed in the network's convention
• Links formatted and counted correctly, including networks that wrap every URL to a fixed width
• Media resized and cropped to the network's aspect ratios

Override anything per network in the composer. What you do not touch follows the main draft.

Networks with no write API

Some networks have no supported way for a server to post for you, and driving a headless browser at one breaks their terms. For those, FoPost stages the post and the browser extension publishes it from your own logged-in session, in one click.

An extension delivery is still a delivery: same calendar, same history, same analytics.

Tokens

Networks issue tokens that expire. They are refreshed in the background before they do, and when one cannot be refreshed the account is flagged and you are told, rather than a scheduled post failing quietly a week later.

Next