Use your own X app to publish without the X allowance

X bills API use per request, and creating a post is one request. When you publish on Publedia's X app, that bill comes to us, so posts to X count against a monthly allowance: 5 on Basic, 30 on Pro and 60 on Ultra. Every post in a thread counts. Once the allowance is used, posts to X stop with Plan limit reached until the first of the next month.

If you register your own app on X, X bills your posts to your X developer account and Publedia stops capping them. Other networks work exactly as before, and your plan's other limits, such as scheduled posts a month, still apply (see plans). For more on posting to X, see how to schedule X posts.

Before you start

You need to be an admin of the workspace. Other members can see the X app row but not change it.

You also need an X developer account, with an app attached to a project on an X plan that allows posting. X sets the price of that plan, so check it with X.

Register the app on X

Screen names follow X's documentation at the time of writing.

1. Open the X developer portal (X's newer documentation calls it the Developer Console). Create an app inside a project, or open one you already have.
2. In the app's user authentication settings, turn on OAuth 2.0.
3. Set the app permissions to read and write.
4. For the type of app, choose Web App, Automated App or Bot. This makes it a confidential client, the kind that gets a client secret.
5. Add this callback URL exactly as shown: https://publedia.com/app/channels/connect/callback
6. Enter your website URL, then save.
7. On the app's Keys and tokens page, copy the OAuth 2.0 Client ID and Client Secret. Do not use the API key and secret from the same page, which belong to a different sign-in method. X shows the secret only once, so paste it into Publedia before you close the page.

Enter the app in Publedia

1. Go to Settings, then Developers, and scroll to Your own platform apps.
2. On the X app row, select Configure.
3. Paste the Client ID and Client secret, then select Save and check.

Publedia asks X to accept the pair before storing anything. If X refuses it, the workspace stays on the app it was using. The secret is stored encrypted and is never shown again. The row then shows Custom app configured instead of Publedia default, with your client ID and when it was checked.

Reconnect every X channel

An X connection belongs to the app it was made through, so changing the app marks every connected X channel Needs reconnection. Open Channels, select Reconnect beside each X account, and approve access while signed in to that same account. See reconnecting a channel.

Scheduled posts are kept. A post that comes due while its channel still needs reconnection fails on X, so reconnect before your next X post is due, or select Retry on the post afterwards.

If you regenerate the secret on X and enter it with the same client ID, your channels stay connected.

Switch back to Publedia's app

Open Configure on the X app row and select Use Publedia's app. Your X channels ask to be reconnected again, and the allowance applies again. Posts already published to X that month count toward it, whichever app sent them.

If something goes wrong

The check on save cannot see the app's callback URL, permissions or app type. X checks them when you reconnect, so a mistake there shows as an error on X's authorization screen. X accepts only an exact callback URL match, so compare it character by character, confirm read and write and the app type, save on X, and select Reconnect again.

If a post to X failed while you were setting this up, see fixing a failed post.