Concepts & glossary

Words we use a lot, defined once. This page is intentionally short — if something’s unclear later, come back here.

Post

A postis the unit of publishing in OpenPost. One post targets one or more channels. When it publishes, each channel gets its own native rendering — a thread on X, a carousel on Instagram, a reel on TikTok — but they share content, metadata, and analytics under one ID.

Channel & integration

A channel is a supported platform: X, Instagram, LinkedIn, TikTok, YouTube, Threads, Facebook, Bluesky. An integrationis your specific connected account on a channel — e.g. @acme_inc on X. One channel can have many integrations.

Integrations have a stable id (e.g. int_abc123). That ID is what you reference in the API. The underlying platform token is refreshed for you — you never handle it directly.

Queue & time slot

Each integration has a queue— a set of recurring time slots. When you schedule a post to “next slot,” we look up the next unfilled slot in that integration’s queue. Queues are the easiest way to maintain a regular posting cadence without picking times manually.

Media

A media asset is an uploaded image or video stored in your workspace. It has its own ID and can be attached to any number of posts. Uploading is done through pre-signed S3 URLs so the file never passes through our servers.

Template

A templateis a reusable post structure — e.g. “Weekly launch update” with placeholder fields, default channels, and a default queue. You create a post from a template and then fill in the blanks.

Workspace

A workspace is your organization inside OpenPost. It owns channels, posts, media, members, and billing. Every API key is scoped to one workspace. Agencies typically have one workspace per client.

Member & role

Members belong to a workspace with one of four roles:

• Owner— full access, including billing and member management.
• Admin— manage channels and members, excluding billing.
• Editor— draft, schedule, and publish posts.
• Viewer— read-only access to analytics and schedules.

Timezone

All times in OpenPost are stored in UTC. We show them in your workspace’s display timezone (set under Settings → Workspace). Each queue can have its own timezone if your audience is in a different region than you.

Schedule times you submit through the API must be ISO 8601 strings with a timezone offset — e.g. 2026-04-20T14:00:00Z or 2026-04-20T10:00:00-04:00.

Notification

A notificationis an event you see in the dashboard: post published, post failed, integration disconnected, billing due. They’re also sent as emails and as webhook events if you subscribe.

Webhook

A webhook is an HTTPS endpoint you register to receive real-time event notifications. Signed with HMAC-SHA256 so you can verify authenticity. See the webhook reference for full details.

API key

An API key authenticates a request to our REST API. Created and revoked under Settings → API Keys. Keys are workspace-scoped and support named prefixes for rotation without downtime.