Every X read is billed to you (X API pricing), so the reads that
would run in the background on an X account are off until you turn them on:
analytics (post metrics and follower counts) and inbox (direct messages).
Neither syncs anything yet; the switches are stored so that both features
respect them when they arrive. Publishing and deleting always work.
Path parameters
profileIduuidRequired- A profile in your organization. Any other value returns 404 profile_not_found.
accountIduuidRequired- An X account in that profile. Another platform's account returns 400 unsupported_platform; any other value returns 404 account_not_found.
Body
xCapabilitiesobjectRequired{ analytics?: boolean, inbox?: boolean }, at least one. Fields you leave out keep their value.
Returns the account with its updated xCapabilities. Turning inbox on needs
the dm.read and dm.write permissions, which a connection made today has not
granted: that returns 409 reconnect_required with the missing scopes in
details.missingScopes.
Errors — 401 unauthorized, 400 invalid_request, 400 unsupported_platform
(not an X account), 404 profile_not_found, 404 account_not_found,
409 reconnect_required, 502 database_error.