---
title: "Get community name, description and member count"
method: GET
path: "/x/communities/{id}/info"
tags: ["Communities"]
---

# Get community name, description and member count

`GET /x/communities/{id}/info`

## Path parameters

- `id` string, required

## Response `200`

Community details

- object
  - `community` object, required — Community info object
    - `id` string, required — Unique community identifier
    - `name` string — Display name of the community
    - `description` string — About text for the community
    - `banner_url` string — Community banner image URL
    - `created_at` string — Community creation timestamp
    - `join_policy` string — Join policy (open or restricted)
    - `invites_policy` string — Invitation policy
    - `is_nsfw` boolean — Whether the community is marked sensitive
    - `creator` object
      - `id` string, required
      - `username` string, required
      - `verified` boolean, required
      - `name` string
    - `member_count` integer — Total member count
    - `moderator_count` integer — Total moderator count
    - `primary_topic` object — Primary topic
      - `id` string
      - `name` string
    - `rules` object[] — Community rules
      - `id` string
      - `name` string
      - `description` string

## Other responses

- `400` — Invalid input
- `401` — Unauthenticated
- `402` — Payment required. Fixed-price direct MPP requests return a Machine Payments Protocol problem document and a WWW-Authenticate challenge. Authenticated X data requests return balances and explicit Stripe checkout-creation actions. Guest paid-read keys receive only the accountless guest top-up action. Direct MPP challenges also advertise the Stripe wallet action. Other authenticated endpoints return a legacy error shape. A failed request never creates checkout. Create checkout only after the user confirms a payment option.
- `404` — Not found
- `424` — Dependency unavailable, unauthorized, or rate limited. Default v1 returns 502. The best-practice response contract returns 424 for transparent dependency failures.
- `429` — Xquik tier rate limit exceeded. The response includes a `Retry-After` header with the number of seconds to wait before retrying.
- `502` — Dependency unavailable, unauthorized, or rate limited. Default v1 returns 502. The best-practice response contract returns 424 for transparent dependency failures.

---

[API](https://skmtc.net/xquik-dev/apis/xquik-api-3.md) · [All operations](https://skmtc.net/xquik-dev/apis/xquik-api-3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/xquik-dev/xquik-api-3/versions/00d8449a6cc1/schema)