Personality — entry 009 of 17
Medium
Medium's REST API lets a registered integration read a user's profile and publish posts on their behalf, gated behind an OAuth-issued integration token (Medium stopped issuing new integration tokens in 2023, but existing tokens still authenticate). A live GET against the real gateway, api.medium.com/v1/me, returned a genuine 401 "An access token is required" JSON error while carrying Access-Control-Allow-Origin: *, resolving cors unknown -> yes and reconfirming OAuth auth in the same probe. No paid tier ever existed for the API itself — pricingModel free.
AuthenticationOAuthRequires an OAuth flow; expect app registration.
HTTPSSupportedTraffic is encrypted in transit.
CORSEnabledCallable directly from browser JavaScript.
PricingFreeNo paid tier — free for the documented use case.
FormatsJSONResponses can be requested as JSON.
GreatAPIs Score
Score57
Authentication8/25OAuth flow required
Pricing20/20Free to use
Docs0/20No docs or spec available
Formats9/15Single response format
Freshness20/20Verified within 6 months
Auth quickstart
- Register an app / run the OAuth flow to obtain a bearer token.
- Send it as an Authorization header
Authorization: Bearer <token>
Stored keyNo key stored
Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.