Commune Event delivery API
Where a newsletter's events go, and how a creator changes it. Communehands every event it publishes to a delivery service that owns fan out,retries, signing and the delivery log, and a destination is one place thatservice sends them: an HTTPS endpoint, or a queue, stream or object storefor a consumer that would rather not run a web server.Reading the list is an operation here, and so is reading the deliveryattempt log: what was handed to which destination, what came back, andasking for one to be handed over again.Changing the destinations themselves is not. `portal-session` mints a linkinto the delivery service's own portal, where a creator adds an endpoint,disables one and rotates a signing secret. Asking for an attempt to bereplayed is the one write here, and is the same action as the portal'sretry button.Needs `webhooks` throughout, since a destination is a private endpoint ofthe creator's, the list of them says which systems a newsletter is wiredinto, and the attempt log says what those systems were told and when.
Commune Event delivery 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 Event Delivery. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 6 JSON Schemas.
This API exposes 5 operations across 5 paths, and defines 20 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 Event delivery 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 5
Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Where a newsletter's events go, and how a creator changes it.
Schemas 20
The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are Article (18 properties), Newsletter (16 properties), Thread (16 properties), DeliveryAttempt (13 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 Event delivery 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.