DEV.to
Markdown articles via your API key, with views and reactions read back.
DEV.to publishing creates an article from your post.
Connecting
Accounts → Connect → DEV.to, paste an API key generated in your DEV.to settings.
What you can publish
| Limit | Value |
|---|---|
| Body | 100,000 characters, delivered as Markdown |
| Title | From the post title, or the start of the body |
| Tags | Up to 4, DEV.to's own ceiling |
| Canonical link | The post's link becomes the article's canonical URL |
| Media | Not uploaded; images must be URLs in the body |
Per post you can publish live (the default) or as a draft on DEV.to.
Analytics
Per article: page views, reactions, and comments. Account-level: follower and article counts. Articles published directly on DEV.to are included in analytics. Competitor tracking works: track any public DEV.to author.
Inbox
Comments on your recent articles land in the inbox. DEV.to's API cannot post comments, so replying happens on DEV.to itself. The inbox links you straight to the thread.
Deleting
DEV.to's API has no delete. Deleting the post in FoPost unpublishes the article: it returns to drafts on DEV.to rather than disappearing.
Next
Related documentation
- Supported Platforms
Every network FoPost publishes to, what each supports, and how each one is delivered.
- Threads
Text, images, video, and carousels on Threads, with follower demographics.
- Bluesky
Posts, threads, video, and analytics on Bluesky, on any PDS, including self-hosted.
- Mastodon
Publish to any Mastodon instance, with visibility controls and the inbox.
- Nostr
Notes and long-form articles published to your own relays.
- MeWe
Text and photo posts to your MeWe profile.
- Pinterest
Image Pins to a board, with impressions, clicks, and saves read back.
- Reddit
Text, link, image, and gallery posts to a subreddit, with the inbox reading replies.