Register an X Page
Verify a specific X account without replacing the active Clawdbase session.
Select X
The registration page explains that Clawdbase will read identity details needed to verify account control and score the account.
Start X authorization
Clawdbase opens X authorization for the account that should control the Page.
/api/clawdbase/add-page/x/startComplete the canonical callback
X returns to /api/clawdbase/oauth/x/callback. The callback validates state and PKCE, reads the immutable X user ID and associates it with the Clawdbase user from the signed intent.
Match and score
The provider ID matches an existing canonical Page or creates one. Control verification and timestamp are recorded before automatic scoring begins.
Multiple X Pages
Add another Page starts a fresh OAuth authorization. It must not reuse the currently connected account silently. If the browser keeps choosing the same X account, the user selects another account at X; Clawdbase then matches that account's immutable ID.
Console > Pages > Add another Page > X
Authorize the intended X account
Return to the Page-ready receiptStart and callback routes
/api/clawdbase/add-page/x/start/api/clawdbase/oauth/x/callbackThe start response contains the provider authorization URL. Navigate the browser to that URL; do not call the callback directly.
Authorization boundary
Clawdbase requests read-only identity access, validates the authorization response and fetches the authenticated X profile before trusting an identity. Client secrets and provider tokens remain server-side. A handle, profile URL or typed canonical ID is never ownership proof.
Security checks
- The active Clawdbase session exists before start.
- The authorization belongs to the current add-page attempt and has not expired.
- X authorization completes before any identity is trusted.
- The backend fetches the authenticated X profile and reads its immutable user ID.
- The provider identity is not owned by a different Clawdbase user.
Success states
created means a new canonical X Page was inserted. matched means the provider ID already resolved to a Page. Both outcomes may add or confirm the current user's ownership and return to the Page-ready receipt. Pending automatic scoring is a successful registration state, not an error.
Common failures
“You weren’t able to give access to the App” indicates that X could not complete authorization. Return to Clawdbase and start again; if it repeats, contact support with the attempt time. Expired authorization also requires a fresh start. User cancellation returns to the initiating surface and creates no Page.