Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
What’s your App ID?
33309410 (Default project-2087897085613867008, Pay Per Use plan)
What endpoint are you using?
POST /2/tweets, GET /2/users/me
What API version are you on?
v2
Are you using a library or SDK? Which one?
No library — custom Python OAuth 1.0a HMAC-SHA1 signing (stdlib hmac/hashlib/base64), HTTP via requests.
What is the issue?
Every OAuth 1.0a user-context request returns 401 Unauthorized, on both a write endpoint (POST /2/tweets) and a read-only endpoint (GET /2/users/me) that requires no elevated permission. This rules out the failure being specific to write scope or to the tweets endpoint.
What is the error message?
{“title”:“Unauthorized”,“type”:“about:blank”,“status”:401,“detail”:“Unauthorized”}
Identical body on both endpoints, no error code (not the classic v1.1-style code 32/89).
When did it start?
First attempt was 2026-08-13. It has never sd again on 2026-08-25.
What have you tried to troubleshoot?
App permissions set to Read and Write, verified in User authentication settings (not just the Keys & Tokens page)
— app type “Web App, Automated App or Bot”, RL configured
Account balance was $0.00 initially → funded to $5.00 and retested — identical 401 (rules out a credits/billing
gate; also the response is a plain 401, not is the documented response for insufficientcredits)
Isolated the failure to the auth layer by nt (GET /2/users/me) with the same OAuth 1.0acredentials used for POST /2/tweets — same 401 body, so it is not write-scope-specific
Regenerated Access Token + Secret once (20changed since app creation
App is attached to the project (Default project-2087897085613867008, Pay Per Use)
This matches the backend-enrollment pattern reported and resolved by X Staff in other topics (e.g. 266297, 263828). Could you please check and fix the backend e410 so OAuth 1.0a user context works?
Thank you!
2 posts - 2 participants
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | OAuth 2.0/authorize fails with 'Something went wrong' on Pay Per Use tier. Al settings verified: billing, enrollment, callback, credentials | 0 | 7.65 | 30-08-2026 |
| 2 | OAuth 2.0 PKCE authorization fails after user approval before callback | 0 | 7.24 | 28-08-2026 |
| 3 | API authorization issue OAuth2 | 0 | 8.78 | 28-08-2026 |
| 4 | OAuth 2.0 regression / authorization rejects numeric-only state values | 0 | 9.79 | 27-08-2026 |
| 5 | Pay-Per-Use: compliance jobs upload_url / download_url return 404 (control plane works) — App ID 33340874 | 0 | 11.64 | 27-08-2026 |
| 6 | X API v2 returns HTTP 500 with empty response body across multiple endpoints | 0 | 8.24 | 27-08-2026 |
| 7 | X Can't post link | 0 | 9.12 | 30-08-2026 |
| 8 | App Suspended (28881659) but Account in Good Standing, can still post | 0 | 8.99 | 27-08-2026 |
| 9 | $200 recurring monthly charges despite project being on pay per use | 0 | 9.39 | 29-08-2026 |
| 10 | Content create vs Post create (Pay per use) | 0 | 9.01 | 29-08-2026 |