Dev.to — how to connect

Publishes articles to your Dev.to (Forem) account — the first line of your post becomes the article title, the rest is the body. No app setup needed: paste your DEV API key (Settings → Extensions → DEV API Keys) when you connect.

Dev.to (Forem) needs no app registration — the operator just generates a personal DEV API key from their own account settings and pastes it in.

Before you start

A Dev.to (Forem) account in good standing — the DEV API Keys panel only appears for accounts with a confirmed email.
A generated DEV API key from Settings → Extensions → DEV API Keys (this is a personal API key tied to your account, not an OAuth app — no app registration or review process needed).
Willingness to publish under your personal profile only: this v1 API key can only create/edit articles owned by the authenticated user, not organization/publication accounts you don't administer.
A post body that reads as an article: the first line becomes the article title (min 1 non-empty character), so an empty or whitespace-only post will fail or publish as "Untitled".

Step by step

1
Log in to dev.to
Sign in to the Dev.to account you want to publish articles from.
Open
2
Open Settings → Extensions
Go to Account Settings and select the Extensions tab in the left panel.
Open
3
Generate a DEV API key
Scroll to the "DEV Community API Keys" section, enter a description, and click Generate API Key.
4
Copy the key
Copy the generated key right away — Dev.to only shows the full value once, immediately after creation.
5
Paste it into the connect dialog
Paste the key into the "DEV API key" field when connecting the Dev.to account in this app.

Paste when you connect

DEV API key (Settings → Extensions → DEV API Keys)secret

Good to know

No OAuth app or approval process is required — it's a personal API key tied directly to the dev.to account, so whoever holds the key can publish as that account.
The key has no visible scopes or expiry in the UI; revoke and regenerate from the same Extensions page if it's ever exposed.
Every publish is a full article (title + markdown body), not a short post — this app derives the title from the first line of the text you write.
Dev.to's API has no delete endpoint, only create and update (PUT), so mistaken posts must be edited or unpublished manually on dev.to.

Troubleshooting

Connect fails with 401 Unauthorized on GET /api/users/me.: The pasted key is invalid, has trailing whitespace/newline, or was revoked/regenerated in Dev.to Settings → Extensions since it was copied. Regenerate a fresh key there and re-paste it exactly, with no extra characters.
Publish fails with a 422 error mentioning the title or body, e.g. article rejected as blank/invalid.: Dev.to requires a non-empty title (derived from your post's first line here). Make sure the first line has real text before whitespace/markdown stripping — a post that's only an image or empty first line will fail; add a short title line at the top.
Requests start returning 429 Too Many Requests when publishing/editing several posts in a row.: Forem enforces a strict per-user rate limit (on the order of ~10 requests/30s, tighter for article-creation endpoints). Space out bulk posts/edits and retry after a short backoff instead of firing them back-to-back.
Publish or edit succeeds against the wrong account, or fails because the key belongs to a different Dev.to user than expected.: DEV API keys are per-account; there's no org/team key. If multiple people share this integration, each must generate and connect their own key from their own Settings → Extensions page — you cannot post to a coworker's profile with your key.

Dev.to developer docs

Before you start

A Dev.to (Forem) account in good standing — the DEV API Keys panel only appears for accounts with a confirmed email.

A generated DEV API key from Settings → Extensions → DEV API Keys (this is a personal API key tied to your account, not an OAuth app — no app registration or review process needed).

Willingness to publish under your personal profile only: this v1 API key can only create/edit articles owned by the authenticated user, not organization/publication accounts you don't administer.

A post body that reads as an article: the first line becomes the article title (min 1 non-empty character), so an empty or whitespace-only post will fail or publish as "Untitled".

Step by step

Open

Open Settings → Extensions

Go to Account Settings and select the Extensions tab in the left panel.

Open

Generate a DEV API key

Scroll to the "DEV Community API Keys" section, enter a description, and click Generate API Key.

Copy the key

Copy the generated key right away — Dev.to only shows the full value once, immediately after creation.

Paste it into the connect dialog

Paste the key into the "DEV API key" field when connecting the Dev.to account in this app.

Good to know

No OAuth app or approval process is required — it's a personal API key tied directly to the dev.to account, so whoever holds the key can publish as that account.

The key has no visible scopes or expiry in the UI; revoke and regenerate from the same Extensions page if it's ever exposed.

Every publish is a full article (title + markdown body), not a short post — this app derives the title from the first line of the text you write.

Dev.to's API has no delete endpoint, only create and update (PUT), so mistaken posts must be edited or unpublished manually on dev.to.

Troubleshooting

Connect fails with 401 Unauthorized on GET /api/users/me.

The pasted key is invalid, has trailing whitespace/newline, or was revoked/regenerated in Dev.to Settings → Extensions since it was copied. Regenerate a fresh key there and re-paste it exactly, with no extra characters.

Publish fails with a 422 error mentioning the title or body, e.g. article rejected as blank/invalid.

Dev.to requires a non-empty title (derived from your post's first line here). Make sure the first line has real text before whitespace/markdown stripping — a post that's only an image or empty first line will fail; add a short title line at the top.

Requests start returning 429 Too Many Requests when publishing/editing several posts in a row.

Forem enforces a strict per-user rate limit (on the order of ~10 requests/30s, tighter for article-creation endpoints). Space out bulk posts/edits and retry after a short backoff instead of firing them back-to-back.

Publish or edit succeeds against the wrong account, or fails because the key belongs to a different Dev.to user than expected.

DEV API keys are per-account; there's no org/team key. If multiple people share this integration, each must generate and connect their own key from their own Settings → Extensions page — you cannot post to a coworker's profile with your key.