Connect X (Twitter) with your own API keys

Tip

The whole setup takes about 5 minutes. The guide looks long only because every screen is captured — the actual flow is short.

Postproxy lets you connect X (formerly Twitter) profiles using your own X developer credentials instead of Postproxy’s shared app. Profiles connected this way are exempt from the shared 24-hour posting quota — your only limit is what your X credit balance and the platform’s per-app rate limits allow.

This guide walks through creating an X developer app on the Pay-Per-Use plan, configuring OAuth 2.0 user authentication for Postproxy’s callback, and saving the app’s Client ID and Client Secret in your Postproxy account.

Note

X uses a Pay-Per-Use credit model. You need to add credits before posting; see X API pricing for current rates.

Step 1: Create a developer account

Open the X Developer Console and sign in with the X account you want to post from. If this is your first time, you’ll see the developer onboarding form: enter an account name, describe your use case, and accept the Developer Agreement and Policy.

After submission, you land on the developer dashboard.

Step 2: Create an app

Open Apps in the sidebar. The page lists apps grouped by environment — Development, Staging, Production. Click Create App in the top right.

Give the app a name and pick Production as the environment, then submit.

X immediately shows a one-time popup with a Consumer Key, Secret Key, and Bearer Token. You can ignore those for now. Close the popup.

The new app appears under Production on the Apps page.

Step 3: Configure user authentication

Open the app to reach its Keys & Tokens tab. Scroll to the bottom and find User authentication settings — click Set up.

In the authentication form, select these options:

• App permissions: Read and write and Direct message (or Read and write if you don’t plan to use DMs)
• Type of App: Web App, Automated App or Bot — this makes the app a confidential client, which is what Postproxy needs for OAuth 2.0

Scroll down to App info and fill in:

• Callback URI / Redirect URL: https://app.postproxy.dev/auth/twitter/callback
• Website URL: https://postproxy.dev (or your own site)

Leave the other fields blank or fill in your own organization details. Click Save Changes.

Caution

The callback URL must match exactly. A mismatch makes the OAuth flow fail with Callback URL not approved.

Step 4: Copy the OAuth 2.0 Client ID and Client Secret

When you save the user authentication settings, X shows the app’s OAuth 2.0 Client ID and Client Secret. Copy both — the secret is only shown once. If you missed it, go to Keys & Tokens and regenerate the Client Secret under OAuth 2.0 Client ID and Client Secret.

Step 5: Save the keys in Postproxy

In the Postproxy dashboard, open Account → BYOK. Make sure the X tab is selected at the top, then in the X (Twitter) card paste your Client ID into App key and the Client Secret into App secret, and click Save keys.

Optionally, tick Pull stats for profiles using these keys to let Postproxy periodically fetch profile and per-post metrics for every X profile connected with this app. It’s off by default and uses your app’s read quota.

From this point, any new X profile connected to your Postproxy account uses your developer app for OAuth.

Step 6: Add credits to your X account

Posting on X requires a non-zero credit balance. Open Billing → Credits in the X developer console.

Click Purchase Credits, pick an amount (or enter a custom value), and continue to payment.

Once you have a payment method on file, you can also enable Auto Recharge so the balance tops itself up when it falls below the threshold.

Step 7: Connect an X profile

Go to Profiles → Connect account → X (Twitter) in Postproxy. You’ll be redirected to X’s authorization screen — approve access and you’ll land back on Postproxy with the new profile connected. The profile is now ready to publish through your developer app.

Reconnecting existing profiles

X profiles that were connected before you saved BYO keys still post through Postproxy’s shared app. To migrate them, disconnect the profile and reconnect it after saving your keys — the new connection picks up your developer app automatically.

If you saved keys back when this page asked for OAuth 1.0a consumer keys, replace them with your app’s OAuth 2.0 Client ID and Client Secret (from the app’s user authentication settings — same callback URL). Profiles still connected under the old keys keep working until you swap the keys; after the swap, reconnect them so they authenticate through OAuth 2.0.

Troubleshooting

Callback URL not approved — the callback in your X app doesn’t match https://app.postproxy.dev/auth/twitter/callback exactly. Check for trailing slashes, http vs https, or typos.

403 Forbidden when posting — your X app permissions are likely set to read-only. Reopen User authentication settings, switch to Read and write and Direct message, save, then reconnect the profile so the new scope takes effect.

Posts fail with a billing or credits error — your X credit balance is empty. Top up under Billing → Credits and enable Auto Recharge to avoid future drops.

Posts succeed in Postproxy but never appear on X — open the post status in Postproxy. If X rejected the post after acceptance (duplicate content, account suspended, media rejected), the platform-level status will show the X error message.