Distribution

Post to X as a Brand Account

Publish to X as a brand handle rather than the developer account that owns your API keys. Click Connect on the X channel, approve the app in a browser signed in to the account you want, and the tokens stay on this device.

Screenshot coming soon

Why you need this

How it changes your marketing workflow

X's developer console hands you an access token for the account that owns the app, which is usually a personal or developer login, not the brand handle you actually want to post from. Getting a token for a different account normally means running an OAuth flow yourself. The X channel's Connect button does that flow for you: sign in to the brand account in your browser, approve the app, and 1MarketingTool stores the resulting tokens locally.

How it works

From open to result in a few steps

1
1

Set up the X app

In console.x.com, set App permissions to Read and write and add http://127.0.0.1:53682/callback as a Callback URI.

2
2

Paste the consumer keys

Copy Consumer Key and Consumer Key Secret from Keys & Tokens → OAuth 1.0 Keys into the X channel and save. The Access Token fields are optional.

3
3

Click Connect

Open the link in a browser already signed in to the account you want to post as, and approve the app.

4
4

Test the connection

Test connection should show that account's @handle. To post as the app owner instead, you can still paste a generated access token.

Without 1MarketingTool

The old, fragmented way vs. one local app

The hard way

# post as @brand, keys owned by @dev
- Generate Access Token → posts as @dev
- run an OAuth 1.0a flow by hand
- paste tokens back into the app

The 1MarketingTool way

X channel → Connect
→ sign in as @brand, approve
→ Test connection shows @brand

Key capabilities

Everything included with Post to X as a Brand Account

Post as a brand handle instead of the app-owner account
Authorize the account through a browser sign-in with Connect
Store the resulting tokens on this device only
Keep pasting an owner access token when you only post as the app owner
Point out-of-credits errors at console.x.com → Billing → Credits

Why it matters

The payoff of having distribution built into your workspace

The right account on every post

The brand handle posts, not whoever registered the developer app.

No manual OAuth

The token exchange runs inside the app.

Fields that match the console

Consumer Key and Consumer Key Secret are labelled the way console.x.com labels them.

Billing errors you can act on

A 402 names X billing and where credits actually live.

Ready to run your marketing locally?

Download 1MarketingTool and use Post to X as a Brand Account alongside 72 other features, all in one app.

Download