Connect DEV

DEV is the odd one out in two ways. It is an article channel rather than a feed, so a post needs a title and a body written in Markdown. And it connects with an API key you paste instead of a Connect screen, because dev.to simply does not offer one.

Connect it

1. On dev.to, open Settings, then Extensions, and scroll to DEV Community API Keys.
2. Give the key a name — “Publiz” does the job — and press Generate API Key. Copy it.
3. In Publiz, open Settings, then Connected Accounts, and press Connect on DEV.
4. Paste the key and save. Your DEV username and avatar appear on the row.

The key covers your whole account

dev.to has no per-app keys, so this one can do anything your account can. Treat it like a password. If you ever want to cut Publiz off, delete the key on dev.to and publishing stops immediately.

The key does not expire, so unlike the other channels you will never be asked to reconnect. A publish that suddenly fails with “the API key is no longer valid” means the key was deleted on dev.to — generate a new one and connect again.

Writing an article

Fill in the title, then write the body in Markdown in the DEV section of the composer. The composer shows a preview as you type.

• Title caps at 128 characters.
• Up to 4 tags. dev.to normalises tags on its side, so one you type may come back slightly renamed or merged into an existing tag. That is their behaviour, not a bug in Publiz.
• Canonical URL, if the piece was published on your own site first. It has to be unique across your published DEV articles.
• Series groups several articles under one name on dev.to.
• Cover image is the first image you attach.

What DEV allows

• Articles of any length — there is no character cap.
• Scheduling works the usual way: pick a time and Publiz publishes it then.
• Editing after publishing works, including swapping the cover.
• Unpublishing turns the article back into a draft on dev.to. It does not delete it, because dev.to’s API has no delete at all. To remove an article for good, delete it from your dev.to dashboard.

Cover images need a paid plan

dev.to does not copy your cover image — it links to the one stored in Publiz and re-fetches it for as long as the article is up. That only works if we keep the file, and the Free plan has no media storage, so articles published on Free go out without a cover. Everything else works the same.

Analytics

You get views, reactions and comment counts per article, refreshed on the usual sync. There are no shares or impressions — dev.to does not count either, so those show a dash rather than a zero.

Follower counts are not available: dev.to has followers in its interface but does not expose the number through its API, so DEV has no audience section.

Comments

dev.to’s API can read comments but cannot post them, so DEV does not appear on the comments page. Replies happen on dev.to itself.

When it doesn’t work

“That API key was rejected.” The key was deleted or regenerated on dev.to. Make a new one and reconnect.

“Hit dev.to’s rate limit.” dev.to allows roughly 10 new articles every 30 seconds. If you schedule a batch at the same minute, some will hit this. They can be retried right away.

A tag went missing. dev.to dropped or merged it on their side. Check the article on dev.to and adjust the tags there or in the composer.