Glossary

The terms FoPost uses, each defined in a sentence or two.

Every term the dashboard, the API, and these docs lean on, alphabetically. Each links to the page that covers it properly.

AI credits

The allowance AI features draw on. Usage is metered in dollars onto the same monthly invoice as everything else and covered by the same free credit; when it runs out, AI calls answer 402 until a card is added or the credit refreshes. See Billing.

API key

The credential for programmatic access, sent in the X-API-Key header. Created in the dashboard with scopes, optionally bound to one workspace, and shown in full exactly once. See Authentication.

Approval

A review step for teams: a post in pending_approval waits until a teammate approves or rejects it, and nothing reaches a platform before that. See Team Collaboration.

Automation

A rule that does publishing work on a trigger: on a schedule, from a feed, or when something calls its API webhook. Each run is recorded, so you can see what an automation did and when. See Automations.

Billing account

Who pays. Workspaces, members, connected accounts, the free allowance, and the monthly credit all roll up to one billing account, so an agency's clients share one invoice. See Billing.

Brand

The whole identity a workspace publishes under: voice and tone for writing, plus colors, fonts, and tagged assets for visuals. One brand per workspace is the default; the agent and AI features fold the brand into what they produce. Called a brand voice in the API. See Brands.

Bulk scheduling

Creating many scheduled posts at once from a spreadsheet import instead of one at a time in the composer. See Bulk Scheduling.

Connected account

One social account on one network, connected through that network's own authorisation. It is the unit pricing meters, and the thing a post's deliveries target. See Connecting Accounts.

Delivery

The per-account copy of a post. One post targeting five accounts has five deliveries, each with its own status, retries, error, and live URL, which is why a post can be partially_failed. See Publishing.

Draft

A post that exists but has no schedule and has not been published. Drafts never reach a platform on their own.

FoPost Agent

The chat surface inside the dashboard: describe what you want in plain language, review the drafts it produces, approve what ships. It can use every capability the product has, and never publishes without your say-so. See FoPost Agent.

Inbox

Comments and mentions from your connected accounts, gathered into one stream you can read and reply from. See Inbox.

Label

A tag on posts (campaign, client, content pillar) and the unit analytics rolls up on, so labelling at publish time is what makes campaign reporting possible later. See Labels.

A hosted page of your links, one URL for the bio field of every network. See Link in Bio.

Media library

The workspace's store of images and video. Uploads, imports from connected sources, and generated images all land here, and everything here is reusable across posts. See Media Library.

Preflight

The pre-publish check: each target account reports ready or blocked with the reasons, plus advisory signals, without anything being sent. See Publishing.

Recycling

Re-scheduling evergreen posts automatically so proven content keeps working without being re-entered. See Recycling.

Scope

A permission on an API key: posts, accounts, webhooks, and so on. A key only reaches endpoints its scopes cover. See Authentication.

Source

An external media provider connected to the library (a design tool or cloud drive) so assets import in place and can be re-pulled when they change upstream. See Sources.

Webhook

A URL of yours that FoPost POSTs signed events to (publish outcomes, delivery failures, account health changes) so you hear what happened without polling. See Webhooks.

Workspace

The isolation boundary everything lives inside: accounts, posts, media, brands, and members with roles. Data never crosses between workspaces, which is what makes one workspace per client safe. See Workspaces.

Related documentation
  • Billing

    When the card is charged, how invoices work, and what the free credit covers.

  • Authentication

    API keys, scopes, and workspace binding.

  • Team Collaboration

    Invite people, set roles, and require approval before anything ships.

  • Automations

    Rules that publish for you, with a run log and a circuit breaker.

  • Brands

    Tone, style, colours, fonts, and assets that AI holds to.

  • Bulk Scheduling

    Import a spreadsheet of posts, validate it, and roll it back if it is wrong.

  • Pricing

    Usage-based - pay per connected social account, every feature included.

  • Connecting Accounts

    Connect a network, keep it healthy, and reconnect when a token expires.

Was this helpful?

On this page