MyPostShare Studio Dashboard: connect accounts, publish posts, and use the Studio API token

MyPostShare has two main experiences. The developer dashboard is for teams that build apps, configure API keys, manage redirect URLs, and set provider credentials. Studio is different. Studio is for the person who wants to sign in, connect social accounts, publish content, and keep their own posting workflow simple.

That distinction matters because many users do not need the full developer console. They need a focused workspace where connected accounts, post creation, delivery status, and a direct posting API token are easy to find. Studio gives them that path without exposing unnecessary admin configuration.

The first step in Studio is connecting social accounts. A user opens the Connections page, chooses a supported platform, and goes through the hosted OAuth flow. MyPostShare handles the provider redirect, token exchange, and connection record so the user can return to Studio with a usable account connection.

Once an account is connected, Studio shows the platform status and the connected username when the provider returns one. That gives the user confidence that posts will go to the correct destination before they publish.

The Compose page is the fastest path for manual publishing. A user writes content, optionally adds media, selects connected platforms, and chooses whether to publish immediately or schedule the post for later.

This workflow is useful for founders, creators, marketing operators, and internal teams that want a simple posting surface without building their own tool. The same backend posting system is used behind the scenes, so Studio posts still produce delivery records and status visibility.

The API Keys tab in Studio is designed for users who want to automate their own posting workflow. The user does not need to create or revoke a token manually. Studio shows a ready token with a copy button, plus examples for each connected platform.

That token authenticates requests to the Studio API endpoint and posts only for the Studio user who owns it. This keeps the workflow simple: connect accounts in Studio, copy the token, and call the direct post API from a script, workflow automation, AI agent, or internal tool.

A Studio API request is intentionally small. The user sends content and a list of connected platforms. If the platform requires media, such as Instagram or YouTube, the request should include a public media URL that the provider can fetch.

For a connected LinkedIn account, a direct post request can look like this:

Without Studio, a user may need to log in to multiple social platforms, remember which account is connected where, and manually repeat the same post across destinations. Studio reduces that friction by putting account connection, post creation, delivery history, and API access in one focused workspace.

The biggest advantage is operational simplicity. A user can publish from the interface when they want a manual workflow, then use the Studio API token when they want automation. Both paths rely on the same connected account state.

Studio is useful when the person posting content is also the person connecting the social accounts. That makes it a good fit for founders, operators, creators, small teams, internal marketing workflows, and automation-heavy users who want direct control.

For SaaS companies that need to embed account connection and publishing inside their own product, the public MyPostShare API and developer dashboard are still the right path. Studio is the lightweight workspace for direct user posting.