# DEV.to

Connect your DEV.to account with an API key.

URL: /docs/providers/devto

You need a DEV.to account, an API key from that account and a DEV.to article channel
in your Postdot project. This is a token connection, not an OAuth redirect flow.

## Create the provider key [#create-the-provider-key]

In DEV.to, open **Settings → Extensions** and generate an API key. Store it privately.
This DEV.to key is different from a Postdot API key: one authorizes the provider
account, while the other authorizes clients of your Postdot instance.

## Connect in Studio [#connect-in-studio]

1. Open your DEV.to channel in **Channels** and start its connection.
2. Enter the **DEV.to API key** and save.
3. Check the DEV.to account shown after verification.

Postdot verifies the key by reading its account identity before storing the
connection. There is no global Postdot OAuth application, client secret or callback
to configure for this provider. Credentials remain on the server after submission.

## Prepare an article [#prepare-an-article]

Use the DEV.to article profile and review its title, body and other required fields
in Studio. An article is not interchangeable with a short social-network message;
check the destination version before scheduling shared source content.

## If the connection fails [#if-the-connection-fails]

An invalid-connection error can mean the key was rejected or no longer works.
Confirm the key belongs to the intended account, generate a replacement if needed,
and reconnect. A provider-unavailable error can also reflect a network or remote
service failure; replacing a valid key repeatedly will not resolve that.

The [Forem API documentation](https://developers.forem.com/api/v1) describes DEV.to's
API-key authentication and article endpoints. Saving a connection does not itself
create or publish an article.