POST https://xquik.com/api/v1/x/communities/{id}/join
10 credits per call · 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.
How to join a community on Twitter through the API
CallPOST /x/communities/{id}/join with one connected Twitter account and
numeric ID. X decides whether that account can join. The route cannot discover,
create, or moderate Communities. Approve each pair first.Understand open, restricted, and invited membership
Open Communities allow direct joins. Restricted Communities may require approval or an invitation. X controls each membership mode. Open the Community page and review its rules. Use the join button for manual membership. Find it at the top of the page. Restricted Communities display Ask to join. A moderator decides that request. No API field selects a mode or accepts an invitation. Use the official X Communities guide for current interface behavior.Find X (Twitter) communities before joining
Existing members can open the Community tab on X.com or iOS. Search by name, description, creator, or handle. X warns that some Communities never appear in search results. Use a direct URL for an account’s first Community. Ask an owner or moderator for the exact link when search omits it. Confirm the specific Community name, description, rules, moderators, membership mode, and recent posts. Never approve membership from a similar display name. Match the numeric ID with Community Info. Community Search searches posts inside one known Community. It cannot find Community directories or topic-based groups.Compare manual and API community joining
For manual membership, sign in to X and open the Community URL. Review the Community rules and membership mode. Select Join or Ask to join. Then wait for any required moderator review. For an API workflow, validate the connected Twitter account and numeric ID. Capture approval before submission. Poll the returned action. Verify the complete member roster after the action reaches a terminal state. X (Twitter) handles invitations, rules, and moderator review for both paths. The API cannot click controls, select a membership mode, or bypass moderator approval.Review account eligibility and moderator limits
Confirm that the X account remains public and connected. Check existing membership and pending requests before submission. Reusing an existing action prevents duplicate membership requests. Admins and moderators enforce each Community’s rules. They review restricted requests. A block between the account and a moderator can stop membership. The API cannot override that relationship. X says an admin account must have a verified email address or phone number. This verified-contact requirement applies only to admins. Each X (Twitter) Community covers one shared topic. The contract defines no separate community account. Store the connected account and Community ID as separate fields.Choose the correct X relationship
- Use Join Community for one approved membership.
- Use Follow for one account relationship.
- Use Create Tweet for an approved Community post.
- Use Community Members to verify the roster.
- Use Community Tweets to read the Community timeline.
Plan post-join reading and publishing
Joining adds one connected account to one Community. It does not create posts, invitations, or moderator changes. Read Community Tweets after confirmation. Store Tweet IDs, replies, reposts, likes, media, and cursors. Use Community Search for keyword matches inside the reviewed Community ID. Read recent conversations before drafting a reply or media post. Membership never authorizes publishing. Approve separate Create Tweet actions for members posting after joining. Keep the reviewed rules with each approval. Avoid repetitive promotions and unwanted invitations. Moderators can remove accounts that violate local rules.Resolve membership intent
Use a numeric Community ID. Record its connected account, membership mode, and approval. Keep enough evidence to explain every membership request.Join an X (Twitter) community step by step
- Review the numeric Community ID and connected account.
- Create one pair-specific
Idempotency-Key. - Submit
POST /x/communities/{id}/joinonce. - Poll the returned action to a terminal result.
- Verify the account through Community Members.
- Store the action, approval, membership mode, and result.
202 confirms processing, not membership. If a timeout occurs, keep
polling the existing action. A changed account or Community needs new approval.
Store the request hash, action ID, status URL, and final membership result. Keep
the same Idempotency-Key only when every input remains identical. A changed
account, Community ID, or approval requires a new key.Join communities in controlled batches
Assign oneIdempotency-Key per approved pair. Process retries serially. Record
each result, action ID, and approval in one stored row. Pause only the
affected account after errors.Verify visible membership
After a terminal result, call Community Members. Follow every cursor. Store the Community ID, action status, matched username, and stable user ID. Never resubmit after checking only one page. Anyone with the direct Community URL can see its member list.Explain community post visibility
Community posts are not private group messages. They can appear on Community pages, profiles, timelines, and search. Review that visibility before approving a post. Anyone on X with the direct Community URL can see the Community’s member list. Joining never publishes a post. Use Create Tweet after separate approval.X (Twitter) community questions
How to join an X (Twitter) community with Xquik?
Review Community Info. Submit one connected account and numeric ID. Poll the action, then verify Community Members.Can I join an invitation-only X (Twitter) community?
For an invite-only Community, X still requires an invitation. Confirm you are logged in to your account on X. This endpoint cannot accept invitations. Save any422 rejection.What happens when you join an X (Twitter) community?
X adds the membership after approval. Members can reply after X confirms membership. They can connect, share posts, and follow the Community’s rules.Can people see the communities you join on Twitter?
Direct Community URLs expose member lists. Posts can also appear publicly.How do I join a community on a phone?
Open a shared Community URL. Review its rules and membership mode. Use X for manual membership or Xquik for server workflows.Do X (Twitter) communities still exist?
Yes. X controls availability, search, membership modes, and moderation.Do I need X Premium to join a community?
The request has no Premium field. X decides account eligibility.Why can’t I join an X (Twitter) community?
Check the public account, numeric ID, connection, mode, and invitation. Check whether the account and moderators block each other. Readterminal,
retryable, and safeToRetry before retrying.How do I find active X (Twitter) communities by interest?
Search the Communities page by topic or creator after joining once. A first membership needs a shared URL. Community Search cannot find Community directories.What are the benefits of joining an X (Twitter) community?
Membership opens one topic-focused discussion space. Members can read its timeline and participate under its rules. This endpoint cannot promise followers, engagement, leads, or sales.How should a brand participate after joining?
Read recent Community posts first. Match the topic and follow moderator rules. Approve each reply, post, and media upload separately. Avoid repetitive promotions and unwanted invitations.Is community notes the same as X communities?
No. Community Notes adds context to posts. X Communities organize memberships and discussions. Use X to join Community Notes.Can this API create, moderate, or grow a community?
No. X stopped accepting new Communities in April 2026. Join Community cannot moderate, invite, or grow members.Recover from join failures
Fix input after400. Replace credentials after 401. Restore credits after
402. Reconnect the account after 403. Check both IDs after 404. Reuse the
same key only for identical input after 409. Save 422 rejections. Honor
Retry-After after 429. Inspect safeToRetry after 500 or 503.
If a connection drops after submission, poll the existing action. Never create
a replacement action after a network error. Keep the original action
after 409. Store X membership rejections after 422. Wait for Retry-After
after 429.
Store the action ID and final membership result.
Never infer posting permission from membership.Headers
Path parameters
Body
Response
- 404 Account not found
Connect the requested account, then submit a newly approved write.
Durable write recovery
- Store
id, the nestedhashinrequest,billing, andstatusUrl. - Poll after
Retry-AfterorpollAfterMswhenterminalisfalse. - Retry only when
safeToRetryistrue. - Use a new key when
nextAction.requiresNewIdempotencyKeyistrue.
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 forRetry-After. FollownextAction.
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_rejected", "message": "X rejected this request. Check what you sent & the account on x.com before you try again." } - 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 }