Commune Sends API
A send is one dispatch of one article to a newsletter's list: when itstarted, when it finished, and the three numbers it finished on. Not tobe confused with Senders, one heading below: a sender is the address anarticle goes out from and is configuration, a send is something thathappened.Starting one is an operation under Articles, because it is a moment in anarticle's life. Reading what became of it is here, because a run is its ownobject with its own identifier and one article can have more than one.The same run is announced as a `send.completed` event, carrying the samethree numbers under the same names, and these operations are how aconsumer reads them back afterwards from the identifier that eventcarried. Needs `sending`.
Commune Sends 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 Sends. 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 16 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 Sends 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 send is one dispatch of one article to a newsletter's list: when it started, when it finished, and the three numbers it finished on.
Schemas 16
The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Article (18 properties), Thread (16 properties), Newsletter (16 properties), Send (10 properties). 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 Sends 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.