X

X requires your own X Developer app. API access, limits, and billing belong to that app. Jak uses OAuth 2.0 user authorization with PKCE.

Configure your X app

1. Open the X Developer Console and create or choose an app with the API access you need.
2. Enable OAuth 2.0 in its user authentication settings and allow read and write access for the supported workflow.
3. In Jak, open Tools → Providers → X → Connect X app and copy the callback URL displayed in the form.
4. Add that exact URL to the X app. Its path ends in /api/v1/oauth/x/callback.
5. Copy the app’s OAuth 2.0 Client ID, and its Client Secret if the client has one. These are different from an app-only bearer token.

See X’s OAuth 2.0 guide for the provider’s setup and client types.

Connect the account

Select the product in Jak. Enter X Developer app Client ID and Client Secret (if your app has one), then choose Continue to X. Authorize the X account you intend the team to use.

Jak requests tweet.read, users.read, tweet.write, and offline.access. Review the consent screen before continuing.

Read and draft

Ask Sasha to inspect the connected account and draft a post for review. Chat tools expose reads, not publishing. Accepting the resulting task does not publish the post.

Publish the finished post

Copy accepted text into X, review the intended account, and publish there. The current app does not have an X publishing control in its browser UI. Connecting OAuth or accepting a task does not enable automatic posting. See Publishing and exports.

Connecting X and connecting Typefully are separate steps; choose the provider where you intend to finish publishing.

If something goes wrong

Check OAuth 2.0 settings, exact callback matching, account permissions, and the app’s API access and usage limits. Reconnect after changing required authorization. This adapter is marked unverified until a permitted live test passes; check its behavior with your own app before relying on publishing.