Skip to main content
POST https://xquik.com/api/v1/x/communities

Why you can’t create a community on Twitter

X stopped accepting new Communities in April 2026. POST /x/communities answers 422 x_community_creation_closed. Xquik charges nothing. Existing Communities still work. Use Join Community to enter one and Community Info to read one. This route does not add rules, members, moderators, invitations, posts, analytics, or membership settings.
0 credits when X refuses the request · All plans from $0.00012/creditA write that must sign in to your X account first adds 10 credits. Xquik refunds them if the sign-in fails. A sign-in that works keeps them, even if X then refuses the write. See the X sign-in fee.

Community creation questions

Do X communities still exist?

Yes. Existing Communities still work, and people post in them every day. X stopped accepting new ones in April 2026.

Do you need X Premium to create a community?

Premium doesn’t help. X refuses new Communities, so an account upgrade doesn’t fix x_community_creation_closed.

Can the API add rules, members, or moderators?

No. The request accepts account, name, and description. Never send undocumented fields.

How should software handle community creation?

Treat 422 x_community_creation_closed as final, and don’t retry it. Send people to an existing Community, an XChat group link or an X List.

Handle creation failures

422 x_community_creation_closed means X isn’t accepting new Communities. Don’t retry it or add credits for it. Xquik charges nothing. A 409 means the key already identifies another request. Compare both request bodies. Reuse the key only when every input matches. After 503, check the write lifecycle before you retry. A disconnected client doesn’t prove failure.

Headers

Body

Response

Connect the requested account, then submit a newly approved write.

Durable write recovery

Send one unique Idempotency-Key per intended write. Replay the same account, target, payload, and media after a lost response. Keep the original key for that replay.
  1. Store id, the nested hash in request, billing, and statusUrl.
  2. Poll after Retry-After or pollAfterMs when terminal is false.
  3. Retry only when safeToRetry is true.
  4. Use a new key when nextAction.requiresNewIdempotencyKey is true.

200 terminal or 202 active

  • After HTTP 200, store the result and settled billing.
  • After HTTP 202, poll the same action. Never submit another write.
  • After HTTP 400, fix the named field. Use a new idempotency key.
  • After HTTP 401, fix authentication. Do not retry unchanged.
  • After HTTP 402, fund the account before another write.
  • After HTTP 403, reconnect the account.
  • After HTTP 409, keep the original action. Use a new key for new input.
  • After HTTP 422, fix the rejected request before retrying.
  • After HTTP 429, wait for Retry-After. Follow nextAction.
See Get Write Action Status for every lifecycle field and terminal state. That page also lists every billing field and retry rule.

Response examples

200 example

202 example

  • 400 { "error": "missing_idempotency_key", "message": "Idempotency-Key is required. Generate one unique key for this write.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true }
  • 401 { "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 404 { "error": "account_not_found", "message": "X account not found. Connect it first at /dashboard/x-accounts." }
  • 409 { "error": "idempotency_conflict", "message": "Idempotency-Key was already used with a different request.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true }
  • 422 { "error": "x_community_creation_closed", "message": "X isn't accepting new Communities, so Xquik created nothing. Xquik didn't charge you. Join an existing Community instead." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 500 { "error": "x_write_failed", "message": "Write action failed unexpectedly. Contact support if this persists." }
  • 503 { "error": "write_tracking_unavailable", "message": "Write tracking unavailable. Try again.", "charged": false, "chargedCredits": "0", "retryable": true, "safeToRetry": true }