> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/lemmy/community>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/lemmy/community.mdx>

---

# Lemmy Community API

One community with its counts, moderators and languages, by name or numeric id.

`GET /v1/lemmy/community?instance=lemmy.world&name=technology` returns `data.community` with `id`, `name`, `title`, `handle`, `host`, `icon`, `banner`, `description`, `publishedAt`, `updatedAt`, `subscriberCount`, `localSubscriberCount`, `postCount`, `commentCount`, `activeUsers`, `postingRestrictedToMods`, `visibility`, `moderators` and `languageIds`.

Ask by `name` or by numeric `id`, not both. A name can be local (`technology`) or remote (`technology@lemmy.world`); a remote lookup through another instance is the network's own resolution, and its counts may be the copy that instance holds. `languageIds` are numeric because the instance's language table is returned by the instance route. A missing community returns `lookupStatus: not_found`.

## Request

- **Endpoint:** `GET /v1/lemmy/community`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by name or id
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/lemmy/community/get)
- **Platform page:** [/platforms/lemmy](https://www.socialfetch.dev/platforms/lemmy)

## FAQ

### Should I ask by name or id?

Give exactly one of name or id. An id is only meaningful on the instance that issued it, so keep the instance beside it. A name is easier to carry between instances.

### How do I resolve a community on another instance?

Use name@host, for example technology@lemmy.world. The instance you ask resolves the remote community, and the counts are the ones it holds for that community.

### What are languageIds?

Numeric discussion language ids. The instance route returns the instance's language table, which maps each id to a code and name.

### How many credits does a community lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.