# Dev.to and Hashnode

> Connect Dev.to or Hashnode so Prefera can post your approved pages there with a link back to the original, and optionally auto-post.

Source: https://prefera.si/docs/integrations/syndication
Docs index for agents: https://prefera.si/llms.txt

Dev.to and Hashnode are for developer and tech audiences. Prefera posts your pages there with a link back to the original, so they reach developers without competing with you in Google.

You find them under **Integrations** > **Developer communities**.

## Connect Dev.to

1. Open dev.to/settings/extensions (**Settings** > **Extensions**).
2. Scroll to **DEV Community API Keys** near the bottom, type `Prefera` as the description and click **Generate API Key**.
3. Copy the key and paste it as **Dev.to API key**. Dev.to shows it once.
4. Click **Test connection**, then **Save and connect**.

## Connect Hashnode

Hashnode needs a Hashnode Pro plan, because Hashnode's API has been Pro-only since May 2026.

1. Open hashnode.com/settings/developer (**Account settings** > **Developer**).
2. Under **Personal Access Token** click **Generate new token** and copy it. Hashnode shows it once.
3. Paste it as **Hashnode personal access token** and click **Find my publications**. Pick your blog under **Publication**.
4. Click **Test connection**, then **Save and connect**.

If the list does not load, open **Or paste the publication id** and paste the 24-character id from your publication dashboard's address (`hashnode.com/<id>/dashboard`).

The key is stored encrypted and never shown again. When editing a saved connection, leave the key empty to keep the saved one.

## What gets posted

Prefera only posts a page you approved. Each post links back to the original page.

- **Dev.to:** the post is sent with the original page as its canonical URL. The text ends with "Originally published at" and the link to the original.
- **Hashnode:** the original page is set as the canonical link (the original article URL) on your publication.

The post uses the page's draft text without its main heading, because the title is its own field. Before posting, the draft goes through the same claim check as any other page. See [Facts and the fact check](/docs/concepts/facts).

Once any platform has a copy up, the page counts as published.

## Auto-syndicate

Once a platform is connected, a switch called **Auto-syndicate published pages** appears. It is **Off** by default.

When it is on and Autopilot publishes a page, Prefera also posts it to your connected platforms that fit your brand. If your brand does not read as a developer brand, Dev.to and Hashnode are skipped. It posts at most three pages a week, and each page only once. If the claim check finds a problem, the post is held for you to review. See [Autopilot and approvals](/docs/autopilot).

## Manage and disconnect

On a connected tile:

- **Test connection** checks the saved key.
- **Manage** lets you replace the key (or change the Hashnode publication).
- **Disconnect** deletes the stored key. Pages already posted stay where they are.

A **Needs attention** badge means the last check failed. Open **Manage** and paste a new key.