---
title: Dev.to API Integration on Truto
slug: devto
category: Marketing Automation
canonical: "https://truto.one/integrations/detail/devto/"
---

# Dev.to API Integration on Truto



**Category:** Marketing Automation  
**Status:** Generally available

## MCP-ready AI tools

Truto exposes 7 tools for Dev.to that AI agents can call directly.

- **list_all_dev_to_me** — Get the Dev.to profile of the user who owns the API key (id, username, name, summary, location, website).
- **list_all_dev_to_articles** — List all of the user's own Dev.to articles, drafts and published, newest drafts first.
- **get_single_dev_to_article_by_id** — Get a single published Dev.to article by its numeric id. Drafts are not returned here; find them with articles list or draft-articles list.
- **create_a_dev_to_article** — Create a Dev.to article from Markdown. Wrap fields under `article`. Set `published: false` to save a draft or `true` to publish immediately. Up to 4 tags.
- **update_a_dev_to_article_by_id** — Update one of the user's Dev.to articles by id. Wrap fields under `article`. Set `published: true` to publish a draft, or `false` to move a published article back to draft.
- **list_all_dev_to_published_articles** — List the user's published Dev.to articles, newest first.
- **list_all_dev_to_draft_articles** — List the user's unpublished (draft) Dev.to articles.

## How it works

1. **Link your customer's Dev.to account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach Dev.to.** The Proxy API is a 1-to-1 mapping of the Dev.to API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Add Dev.to as a content syndication channel in your CMS** — Let technical content teams push Markdown articles from your headless CMS directly to Dev.to with canonical URLs preserved, so they capture developer reach without sacrificing SEO on their primary domain.
- **Expand your social scheduler to reach developer audiences** — If you build a content scheduling or marketing automation tool, Dev.to is a non-negotiable channel for DevRel teams. Offer scheduled publishing and edits to Dev.to alongside X and LinkedIn in a single workflow.
- **Enable draft sync from documentation and writing tools** — Allow users of your docs platform or writing app to continuously sync in-progress content to Dev.to as drafts, so authors can switch to the Dev.to UI only for the final publish step.
- **Auto-populate developer portfolios and community profiles** — If you build portfolio sites, link-in-bio tools, or community dashboards, pull a user's Dev.to profile and published articles to keep their 'latest writings' feed fresh without manual updates.
- **Power DevRel analytics and content inventory tools** — Give DevRel managers a unified view of what's live versus still drafting across their stack by mirroring their Dev.to article inventory into your reporting or content ops product.

## What you can build

- **One-click cross-post to Dev.to** — Ship a toggle inside your publishing flow that pushes Markdown to Dev.to via create_a_dev_to_article with tags and canonical URL set automatically.
- **Scheduled Dev.to publishing** — Let users queue articles in your UI and trigger create_a_dev_to_article at the scheduled time, with update_a_dev_to_article_by_id handling last-minute edits.
- **Draft-first review workflow** — Push content as published: false so a DevRel lead can review in Dev.to, then flip to published: true via update_a_dev_to_article_by_id when approved.
- **Live portfolio widget** — Use list_all_dev_to_me and list_all_dev_to_published_articles to render a dynamic 'Latest on Dev.to' section on your users' profile pages.
- **Content inventory dashboard** — Combine list_all_dev_to_published_articles and list_all_dev_to_draft_articles to show users exactly what's live, what's in draft, and what needs attention.
- **Profile auto-enrichment on signup** — Call list_all_dev_to_me after OAuth to pre-fill username, bio, avatar, and website in your onboarding, skipping manual profile setup for developer users.

## FAQs

### How does authentication to Dev.to work through Truto?

Dev.to uses API key authentication. Truto handles secure storage and injection of each end user's API key, so your product never needs to touch or manage credentials directly.

### Can we publish articles in Markdown?

Yes. create_a_dev_to_article accepts raw Markdown as the body, which is the native format Dev.to authors use. You can also set tags (up to 4), a canonical URL, and the published state in the same call.

### Can we preserve SEO when cross-posting from our own site?

Yes. The create and update article endpoints support setting a canonical URL, so Dev.to will attribute SEO value back to the original source when syndicating content.

### Can we manage drafts versus published articles separately?

Yes. list_all_dev_to_draft_articles and list_all_dev_to_published_articles let you fetch each state independently, and update_a_dev_to_article_by_id can toggle the published flag to move an article between draft and live.

### Does the integration support reading comments, reactions, or follower data?

Not currently. The available tools cover profile (list_all_dev_to_me), article listing, article retrieval, and article create/update. If you need additional endpoints, Truto can add them on request.

### How fresh is the article data we fetch?

Calls are made in real time against the Dev.to API, so list and get operations return the current state at request time. There is no intermediate cache that could stale the data.

### What about Dev.to rate limits?

Dev.to enforces per-user rate limits on article creation and updates. Truto surfaces rate limit errors transparently so you can implement retry or queueing logic appropriate to your publishing workflow.
