API archive entry · source-reported
Medium
Community of readers and writers offering unique perspectives on ideas
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
This repository contains the documentation for Medium’s API. Medium’s API is a JSON-based OAuth2 API. All requests are made to endpoints beginning: https://api.medium.com/v1 All requests must be secure, i.e. https, not http. By using Medium’s API, you agree to our terms of service. In order to publish on behalf of a Medium account, you will need an access token. An access token grants limited access to a user’s account. We offer two ways to acquire an access token: browser-based OAuth authentication, and self-issued access tokens. We recommend using self-issued access tokens. Browser-based authentication is supported for existing integrations only. Self-issued access tokens (described in user-facing copy as integration tokens) are explicitly designed for desktop integrations where implementing browser-based authentication is non-trivial, or software like plugins where it is impossible to secure a client secret. You should not request that a user give you an integration token if you don’t meet…
Read the full README ↗ · Preview checked 2026-10-29T05:30:45.773Z
Inside the original README — Document outline
- Medium’s API documentation
- Contents
- 1. Overview
- Developer agreement
- 2. Authentication
- 2.1. Self-issued access tokens
- 2.2. Browser-based authentication
- 3. Resources
- 3.1. Users
- Getting the authenticated user’s details
- 3.2. Publications
- Listing the user’s publications
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
Where these facts came from
AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.
What is reported
- Name, category, and short description
- Authentication label
- HTTPS and CORS labels
- Provider/source URL
What is not established
- Current uptime or availability
- Pricing, quotas, and rate limits
- Security, compliance, or licensing posture
- SDK quality or endpoint completeness
Record checkpoints
- First observed: Sep 14, 2026
- Last directory-field change: Sep 14, 2026
- Current source observation: Oct 30, 2026
Source reference
This page separates source-reported facts from questions that need live provider verification.