Concepts

Workspace

Your Crier account is a workspace: it has a team (owners, admins and members), a balance, its API keys and its webhooks. An API key acts on the whole workspace. See Team and roles and Balance and billing.

Profiles

A profile (prf_…) is a brand or a customer. It groups their accounts, their queue and their time zone. If you build a platform, create one profile per customer and keep your own id in externalId. Every workspace starts with one profile, “Mi marca”, which can be renamed or deleted.

Accounts

An account (acc_…) is a social account connected to a profile through the connect flow. Its status says whether it can publish: active, or needs_reconnection when the network withdrew the permission and it has to be connected again. GET /v1/accounts/health checks the accounts against each network.

Posts

A post (pst_…) has text, images or videos and one or more targets: the accounts it goes out on, each with its own text and network options.

Status	Meaning
`draft`	Saved without a date. Also a post rejected in review.
`pending_approval`	Waiting for an owner or admin to approve it.
`scheduled`	Scheduled for `scheduledFor` (or the next queue slot).
`publishing`	Going out on the networks.
`published`	Published on every target.
`partial`	Published on some targets and failed on others. Each target says its error.
`failed`	Did not go out anywhere. Retry with `POST /v1/posts/{id}/retry`.
`cancelled`	Cancelled before going out.

Each target has its own status and, once out, the post’s url on that network.

Ids

Every id is Crier’s and has a prefix that says what it is: prf_, acc_, pst_, grp_ (account groups), cs_ (connect sessions), evt_ (webhook events). Inbox ids (cnv_, thr_, cmt_, mtn_, rev_) are opaque: use them as they are, without parsing them.

Dates and time zones

Dates are ISO 8601. When scheduling, send the time with its offset (2026-10-30T09:00:00+01:00) or a local time with timezone (Europe/Madrid). Responses come back in UTC.

Pagination

Long lists return nextCursor. Pass it as cursor in the next request; when it is null, there is nothing more.

{
  "data": {
    "items": [],
    "nextCursor": "eyJ…"
  }
}