Commune Articles API

An article is one thing a newsletter published: written in Commune and sent, or imported from the newsletter's provider. Two rules gate every article read and are described on each operation. First, an article stamped with an audience is visible only to the newsletter's team and to subscribers holding one of its tags. Second, an article dated in the future is invisible until that moment passes. An article written in Commune can be created and edited here, its body sent and returned as Markdown, and moved through its life: sent to a test address, queued for a time, taken back off the schedule, sent to the list, and re-attempted for the recipients a dispatch could not reach. An imported article is read only. What one reader did with an article is here too, from their side of it. `GET /saved-articles` and `GET /liked-articles` are the articles an account put aside and the articles it liked, across every newsletter it reads, and they need `account: read` rather than `content`. Both obey the two rules above, applied against the person rather than against a newsletter, so an article they may no longer read leaves the page on its own.

Operations 12

GET /newsletters/{newsletter}/articles List a newsletter's articles #
POST /newsletters/{newsletter}/articles Create an article #
GET /articles/{article} Retrieve an article #
PATCH /articles/{article} Edit an article #
GET /articles/{article}/authors List an article's authors #
POST /articles/{article}/images Store an image for an article #
POST /articles/{article}/test-send Send a test copy of an article #
POST /articles/{article}/schedule Schedule an article #
POST /articles/{article}/unschedule Cancel a scheduled article #
POST /articles/{article}/send Send an article to the list #
GET /saved-articles List the articles this account saved #
GET /liked-articles List the articles this account liked #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/usecommune:usecommune-articles-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

usecommune-articles-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Usecommune Articles API
  version: '2026-08-26'
  contact:
    name: Commune
    url: https://usecommune.com
    email: support@usecommune.com
  description: 'Operations tagged Articles across 2 of this provider''s published API definitions: usecommune-openapi.json, usecommune-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.usecommune.com
  description: 'Production. There is no separate sandbox host.

    '
security:
- apiKey: []
tags:


# --- truncated at 32 KB (128 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/usecommune/refs/heads/main/openapi/usecommune-articles-api-openapi.yml