Reference
Glossary
The ten words that mean something specific here. Most of them are ordinary words we use narrowly, which is exactly when a glossary earns its place.
What do I own in uplika?
Three things: workspaces, the channels connected inside them, and the keys that reach them. Everything else is derived from those.
- Workspace
- A brand's own compartment. Channels, posts, keys and logs all live inside one and never leak across. One account can hold as many as it likes; they are partitions for one person, not seats for a team, so there is no inviting anyone into one.
- Connected channel
- One social account you have authorized us to post to, held inside one workspace. The same social account can be connected in two workspaces and each connection carries its own token.
- API key
- A secret that reaches exactly one workspace over REST. We show it once and store only a hash, so a lost key is replaced rather than recovered. Revoking one keeps its row so old log lines still point somewhere.
How does an agent get in?
Not with a key. An agent authorizes itself over OAuth and holds a token scoped to what you approved.
- MCP authorization
- The flow where an agent registers itself, sends you to an approval screen, and receives a token. Nothing is pasted into the agent by hand. The token covers the whole account, so the agent can reach every workspace you own.
- Scope
- One permission on a token, like posts:write. A read-only key simply does not carry the write scopes, so publishing fails at our door instead of the platform's.
- Account verification gate
- Email and phone both confirmed. Until both are done there is no workspace at all, and an unfinished signup is deleted within a day so the address and number go back into circulation.
What are the moving parts of one publish?
A publish is not one thing. It is a target per channel, a container per platform, and a link that only exists at the end.
- Target
- One post going to one channel. Publishing to several channels makes one post and one target per channel, and each can succeed or fail on its own. That is why a post can come back partly published.
- Container
- Meta's two step publish: we create a container, the platform processes it, then we publish it. Video containers take the longest, which is why a publish can still be in flight when we answer.
- Presign
- A short lived URL that lets a file be uploaded straight to our storage without passing through the API. The bytes never touch our server, so a large video does not tie up a request.
- Permalink
- The public address of a published post. It does not exist until the platform has actually published, which is why it is null in the response you get right after calling publish.
Questions
Is a workspace the same thing as a team?
No. There are no members and no invitations. A workspace is one person's compartment for one brand, and the only way anyone else reaches it is by holding your key or your agent's token.
Why does my post say partly published?
Because a post has one target per channel and they settle separately. Some went out and some did not. Retrying sends only the ones that failed, so nothing gets posted twice.
Why is the permalink null right after I publish?
Because publishing is asynchronous. We answer as soon as the work is accepted, and the link exists only once the platform finishes. Call get_post again, or pass wait: true and we will hold the answer for you.