Commune Users API
A person with a Commune account: the readers who join a community and thewriters who are credited on an article. Looked up by identifier or byusername, and only ever as a public profile: never an email address.The one account read from the inside is the credential's own. `GET /me`is the same person as the profile above plus the address and verificationstate that one withholds, and it sits here rather than under a heading ofits own because it is the private view of exactly what this tag alreadydocuments. It needs no permission at all.
Commune Users API is one of 18 APIs that Commune publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 6 JSON Schema definitions.
Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 6 JSON Schemas.
This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2026-08-26.
Requests are made against a single base URL, https://api.usecommune.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Commune Users API declares
2 security schemes
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 13 scopes.
It accepts HTTP bearer tokens (Commune API key) (apiKey).
By default, every request must be authenticated.
oauth2— An OAuth access token, sent as Authorization: Bearer . The walkthrough of the whole flow is at [usecommune.dev/use-cases/build-an-integration](https://usecommu…apiKey— A Commune API key, sent as Authorization: Bearer . A key is granted one or more newsletters and carries six permission families on each, every one of them none…
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
A person with a Commune account: the readers who join a community and the writers who are credited on an article.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Me (8 properties), User (5 properties), Error (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Commune 12
Other APIs Commune publishes across the network.
This is an independent, third-party profile of Commune Users API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.