DEV Community · Authentication Profile

Devto Authentication

Authentication

DEV Community secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

Developer CommunityArticlesBloggingSocialContentOpen-Source
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

api-key apiKey
· in: header (api-key)

Source

Authentication Profile

Raw ↑
generated: '2026-07-11'
method: derived
source: openapi/openapi.json, openapi/openapi.yaml
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: api-key
  type: apiKey
  in: header
  parameter: api-key
  description: "API Key authentication.\n\nAuthentication for some endpoints, like write operations\
    \ on the\nArticles API require a DEV API key.\n\nAll authenticated endpoints are CORS disabled,\
    \ the API key is intended for non-browser scripts.\n\n### Getting an API key\n\nTo obtain\
    \ one, please follow these steps:\n\n  - visit https://dev.to/settings/extensions\n  - in\
    \ the \"DEV API Keys\" section create a new key by adding a\n  "
  sources:
  - openapi/openapi.json
  - openapi/openapi.yaml

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact
curl "https://apis.io/api/v1/security/devto-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.