devto.article

curl "https://api.onekey.dev/v1/devto/article?id=270180" \
  -H "x-api-key: YOUR_API_KEY"

{
  "success": true,
  "data": {
    "content": {
      "id": "270180",
      "title": "Changelog: Query the DEV API from a JavaScript Frontend!",
      "url": "https://dev.to/devteam/changelog-query-the-dev-api-from-a-javascript-frontend-329j",
      "text": "We recently updated the DEV API to allow it to be queried directly from JavaScript frontends....",
      "createdAt": "2020-02-27T16:12:29Z",
      "language": null
    },
    "author": {
      "username": "rhymes",
      "displayName": "rhymes",
      "id": "2693",
      "avatarUrl": "https://media2.dev.to/dynamic/image/width=640,height=640,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2693%2Fbfd9a4a5-92b3-4ac3-a276-3ccb68d78203.jpg"
    },
    "engagement": {
      "likes": 84,
      "comments": 5,
      "views": null
    },
    "media": {
      "thumbnailUrl": null
    },
    "ext": {
      "contentBody": "We recently updated the [DEV API](https://docs.dev.to/api) to allow it to be queried directly from JavaScript frontends.\n\n{% github https://github.com/thepracticaldev/dev.to/pull/6116 %}\n\nA persistent problem with querying the DEV API is the [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) restriction. `CORS` (Cross-Origin Resource Sharing) is a built-in mechanism that enables browsers to access resources belonging to another origin when initialized by scripts. This mechanism means that a page at `http://example.com` can only access data at its *own* resources (for example, `example.com/hello`) but it cannot access a resource at another domain (for example, `anotherdomain.com/hello`). If the HTTP server on `anotherdomain.com` wants to let a script running on `http://example.com` (or any other website) access its own resources, it has to do it through `CORS`.\n\nFor DEV community members, this restriction meant that having to create [some workarounds](https://dev.to/jrsofty/cors-problem-workaround-for-consuming-dev-to-api-on-your-website-44jb) for this issue. But with this change, everyone can now retrieve publicly-available endpoints directly from their own browsers. The one caveat here is that the endpoints that can be queried are limited to the ones that require no authorization (ie. no `api-key` header).\n\nHere's an example of a query to the `/api/articles` endpoint from the JavaScript console:\n\n![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/ftm5s1l4nqpmx",
      "readingTimeMinutes": 1
    }
  },
  "metadata": {
    "platform": "devto",
    "endpoint": "article",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 1,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}