Marketing Automation
Dev.to
API integration
Ship Marketing Automation features without building the integration. Full Dev.to API access via Proxy and 7 MCP-ready tools for AI agents — extend models and mappings to fit your product.
Talk to usUse Cases
Why integrate with Dev.to
Common scenarios for SaaS companies building Dev.to integrations for their customers.
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
Ship these features with Truto + Dev.to
Concrete product features your team can ship faster by leveraging Truto’s Dev.to integration instead of building from scratch.
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.
SuperAI
Dev.to AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
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.
Why Truto
Why use Truto’s MCP server for Dev.to
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Start with Dev.to in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.
Link your customer’s Dev.to account
Use Truto’s frontend SDK to connect your customer’s Dev.to account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Dev.to
Truto’s Proxy API is a 1-to-1 mapping of the Dev.to API. You call us, we call Dev.to, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Dev.to’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Dev.to on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
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.
Dev.to
Get Dev.to integrated into your app
Our team understands what it takes to make a Dev.to integration successful. A short, crisp 30 minute call with folks who understand the problem.