DEV (dev.to) integration
No native DEV (dev.to) connector, here is what does work.
We cross-post to DEV with canonical URLs pointing at your domain, on a deliberately human cadence.
How it works
DEV runs on Forem, and its API v1 authenticates with an api-key header. Articles carry a published flag, false for draft and true for live, and the API has no scheduling, so timing is on the client. We queue approved posts and make the publish call at the time you chose, which gives you scheduling the platform itself does not offer.
DEV is a community first, and it moderates like one: automated bulk posting reads as spam and gets treated accordingly. Our positioning is cross-posting, not primary publishing. Every article carries a canonical_url pointing at your own domain, cadence defaults are conservative and human-paced, and we never bulk-dump a backlog into the feed. Done this way, DEV adds a developer audience to work that already lives on your site.
Best forCompanies with developer-relevant content on their own site who want the DEV audience reading it without risking community standing.
Setup, step by step
- Generate an API key in your DEV account settings under Extensions.
- Add the key to SearchHandled's DEV connector.
- Set your canonical policy, pointing each cross-post at its original on your domain.
- Choose a posting cadence, and note that our defaults are deliberately conservative for this channel.
- Pick draft-first review in DEV or scheduled direct publishing per post.
Best practices
Always cross-post, never orphan
Publish on your own site first, then cross-post to DEV with canonical_url set. Your domain keeps the search value, and the DEV copy exists purely for that community's readers.
Keep a human cadence
A steady trickle of genuinely relevant posts builds standing on DEV. A dump of ten articles in an afternoon reads as spam to both moderators and readers, so we do not offer bulk publishing here.
Choose tags like a member
DEV's discovery runs on a small set of tags per post. We pick the few that honestly fit, because tag-stuffing is visible to the community and works against you.
Engage where you post
Cross-posting works best when someone from your team occasionally answers comments. We handle the publishing, but a little human presence in the threads is what makes the channel compound.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
No scheduling in the API
The Forem API has a published flag but no scheduled publish time, so posts go live whenever the call is made.
How we handle itWe queue approved posts and make the publish call ourselves at the time you chose, which restores scheduling on top of an API that lacks it.
developers.forem.com
Community moderation on automated content
Automated bulk posting patterns trip DEV's spam moderation, and accounts posting that way can lose standing or visibility in the community.
How we handle itOur cadence defaults are conservative, every post carries canonical attribution to your domain, and we never bulk-dump a backlog. The pipeline is built to look like what it is, a person's worth of publishing.
developers.forem.com
Questions teams ask
- Why not use DEV as our main blog?
Because the content would live on a platform you do not control, and DEV's own culture favors cross-posting with attribution. Publishing on your domain first and cross-posting with canonical_url gets the audience without giving up the asset.
- How does scheduling work if the API has none?
We hold approved posts in our queue and fire the publish call at the scheduled moment. From your side it works like scheduling anywhere else; the timing just lives in our pipeline instead of DEV's.
- Will automated posting get our account flagged?
Bulk automated posting can, which is why we refuse to do it. Conservative cadence, canonical attribution, and honest tagging keep the account looking like the genuine contributor it is.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us DEV (dev.to) matters moves it up the rollout.