Skip to content
GET /v1/article

A single article with full markdown body

Try it live

10 free calls per day — no sign-up, no API key. Goes through the oanor gateway.

Custom headers (optional)
api.oanor.com/devto-api

It works. Grab an API key and use it in your project.

Get an API key

Code snippets

curl "https://api.oanor.com/devto-api/v1/article" \
  -H "x-oanor-key: oanor_test_..."
await fetch("https://api.oanor.com/devto-api/v1/article", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
$ch = curl_init("https://api.oanor.com/devto-api/v1/article");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);
import requests
requests.get(
    "https://api.oanor.com/devto-api/v1/article",
    headers={"x-oanor-key": "oanor_test_..."}
)

Example response

A real response from this endpoint, captured by the latest health check.

{
    "data": {
        "article": {
            "id": 5,
            "url": "https://dev.to/ben/dhh-on-the-future-of-rails",
            "tags": "ruby, rails",
            "user": {
                "name": "Ben Halpern",
                "github": "benhalpern",
                "twitter": "bendhalpern",
                "username": "ben"
            },
            "title": "David Heinemeier Hansson on the Future of Rails",
            "author": {
                "name": "Ben Halpern",
                "username": "ben"
            },
            "comments": 2,
            "edited_at": null,
            "reactions": 26,
            "cover_image": "https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/http%3A%2F%2Fi.imgur.com%2FQb20fNn.jpg",
            "description": "\n\nThe Ruby on Rails framework has had an incredible impact since its creation a d...",
            "published_at": "2016-01-05T15:41:22Z",
            "body_markdown": "<p>The Ruby on Rails framework has had an incredible impact since its creation a decade ago, becoming the choice for some of today's mightiest tech companies. Patterns and concepts popularized by the framework have also had an indelible effect on the application architecture discussion. Rails is an open-source project which depends on innovation and good software design from its core team in order to maintain its direction and status. New paradigms are constantly emerging&nbsp;and Rails has done well to evolve and remain the go-to for many developers.&nbsp;</p>\r\n<p>Rails is an open-source project which depends on innovation and good software design from its core team in order to maintain its direction and status. So much of Rails' direction depends on the views of its opinionated&nbsp;creator&nbsp;and&nbsp;Basecamp CTO&nbsp;<a href=\"https://twitter.com/dhh\">David Heinemeier Hansson</a>. I contacted David in order to glean some insight into the direction of Rails. David shared his vision of the future with Practical Developer.&nbsp;</p>\r\n<h2>A lot has happened since Rails 4.0 was released in summer of 2013, particularly in the Node community. Where does Rails fit in now compared to the past?&nbsp;</h2>\r\n<p>Ruby on Rails has its eyes on the same prize its always had: Be the full-stack framework that makes building applications like Basecamp, Github, Shopify, Kickstarter, Airbnb, Zendesk and others possible and enjoyable for small teams. Programming never stands still, of course. We've seen Node, Elixir, Go, Rust, and all sorts of other languages and frameworks come, and that's wonderful. The more the merrier! The web is an amazing platform exactly because it puts all these approaches on a level playing field when it comes to generating HTML, JavaScript, CSS. On the web nobody knows whether your web server is running Ruby or Go or Node. For me, the projects I make, and the examples I listed above, though, I have yet to see anything that really gives Rails a serious run for it
…