Connect DEV Community first
- 01
In DEV settings, create an API key.
- 02
Open Accounts in 1Post and choose Connect, then DEV Community.
- 03
Paste the API key.
- 04
Choose the account in the composer.
Then GET /v1/accounts returns the id of the DEV Community account to use in the request.
Send a post to DEV Community
curl https://api.get1post.com/v1/posts \
-H "Authorization: Bearer $ONEPOST_API_KEY" \
-H "Idempotency-Key: devto-first-post" \
-d '{"accounts":["ACCOUNT_ID"],"text":"What changed in version 2.","schedule_at":"2026-11-02T15:00:00Z"}'The reply is 202 with the post (status scheduled) and one destination for DEV Community, which moves from queued to published or failed.
What you can send to DEV Community
- Article
- Cover image
- Tags
- Canonical URL
What DEV Community publishes
- An article takes up to 4 tags, a canonical URL and a cover image address.
DEV Community rules the request is checked against
| Rule | What 1Post checks |
|---|---|
| Text limit | No length check |
| Media accepted | Images |
| Images per post | 1 |
| Threads | No |
| First comment | No |
| Posts per day, per connected account (1Post) | 5 |
The same table with sources is on the DEV Community specs page.
Good to know for DEV Community
A DEV Community article carries a cover image, up to 4 tags and an optional canonical URL, so a post first published on your own site stays credited to it.
Check the post before it is queued
Add "dry_run": true to test a post: nothing is kept, a valid one answers 200 and a broken one answers 422 naming the rule.
{
"error": {
"code": "invalid_for_platform",
"message": "devto refuses this post: DEV Community needs some content. (empty_text).",
"fix": "Fix the rule named in the message and send the post again.",
"retryable": false,
"request_id": "REQUEST_ID"
}
}An assistant connected to the MCP server sends the same fields to create_post; set one up.