Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Credits added to wrong developer account — which app/account should I use?

Дата публикации: 27-08-2026 15:16:48


Hello,
I manage @MarlowStudent from my account @Tally__DE. I mistakenly created a separate developer account for @MarlowStudent and added prepaid API credits there, rather than authorizing @MarlowStudent through the app on my existing developer account. I accept responsibility for that mistake and want to correct the setup without running duplicate apps or stranding the credits.
Current setup:
@Tally__DE developer account 2058284019742097409 — app 32973549
@MarlowStudent developer account 2088279883528998912 — app 33313442, where the credits were purchased
@MarlowStudent is also currently suspended. Before the first suspension, his final two API actions were separate one-to-one replies to users who had directly mentioned him. They were dispatched 2.44 seconds apart at about 03:06 BST on 24 August. I found no unsolicited replies, but I accept responsibility for allowing those replies to be sent so close together and will prevent clustered dispatches. The account was later restored, made no further X posts or replies, and was suspended again by the following morning. An appeal is pending.
Should I keep app 33313442 under the @MarlowStudent developer account so its credits remain usable, or should I authorize @MarlowStudent through app 32973549 under @Tally__DE?
Can @Tally__DE be added as an administrator/team member for app 33313442, or is there another supported way to manage it without losing access to the existing credits? Does the current suspension prevent this, and which support route should I use?
Thank you.
3 posts - 2 participants
Read full topic

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1$200 recurring monthly charges despite project being on pay per use09.3929-08-2026
2Account automation not working anymore07.9827-08-2026
3App Suspended (28881659) but Account in Good Standing, can still post08.9927-08-2026
4X and Grok Bot Voucher010.7830-08-2026
5OAuth 2.0/authorize fails with 'Something went wrong' on Pay Per Use tier. Al settings verified: billing, enrollment, callback, credentials07.6530-08-2026
6Content create vs Post create (Pay per use)09.0129-08-2026
7Do human-reviewed AI reply suggestions need additional approval?09.9827-08-2026
8Ads API 403 and App Manager cannot resolve JTP iOS and Android identifiers07.8828-08-2026
9Approval request: AI-powered mention-triggered reply bot (@MarlowStudent, App ID 32973549)09.9830-08-2026
10Problems between X and Grok Bot06.6228-08-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 6.39. Источник: twittercommunity.com.