How medium/medium-api-docs works
This repository is API documentation, not an API implementation. Its documented user-to-result workflow is to obtain an access token—preferably a self-issued integration token, or through browser OAuth for existing integrations—and use it for Medium API requests. The README identifies user profiles, publications, posts, and images as resource areas. The tree contains only README.md, so these nodes represent documented concepts; no implementation internals or resource-level request wiring can be verified.
Main entry points: README.md API guide
Components 11
Authentication
- Browser OAuth
README.md - Self-issued token
README.md - Token endpoint
README.md - Access token
README.md
API resources
- User profiles
README.md - Publications
README.md - Posts
README.md - Images
README.md
Other components
- Integration developer
- API guide
README.md - Medium API
Connections 17
- API guide → Browser OAuth: documents
- API guide → Self-issued token: documents
- API guide → User profiles: documents
- API guide → Publications: documents
- API guide → Posts: documents
- API guide → Images: documents
- Integration developer → Browser OAuth: authorizes via
- Browser OAuth → Token endpoint: exchanges code
- Integration developer → Self-issued token: generates token
- Token endpoint → Access token: returns token
- Self-issued token → Access token: provides token
- Integration developer → Medium API: sends authenticated requests
- Medium API → User profiles: serves resource
- Medium API → Publications: serves resource
- Medium API → Posts: serves resource
- Medium API → Images: serves resource
- Access token → Medium API: authenticates requests