Connect Kick first
- 01
Open Accounts in 1Post and choose Connect.
- 02
Pick Kick.
- 03
Sign in with Kick and approve access for the channel you want to post to.
- 04
Choose the channel in 1Post. It is ready to pick in the composer.
Then GET /v1/accounts returns the id of the Kick channel to use in the request.
Send a post to Kick
curl https://api.get1post.com/v1/posts \
-H "Authorization: Bearer $ONEPOST_API_KEY" \
-H "Idempotency-Key: kick-first-post" \
-d '{"accounts":["ACCOUNT_ID"],"text":"Going live in ten minutes.","schedule_at":"2026-11-02T15:00:00Z"}'The reply is 202 with the post (status scheduled) and one destination for Kick, which moves from queued to published or failed.
What you can send to Kick
- Chat message in your own channel
Kick rules the request is checked against
| Rule | What 1Post checks |
|---|---|
| Text limit | 500 characters, counted by the characters a reader sees |
| Media accepted | Text only |
| Threads | No |
| First comment | No |
| Posts per day, per connected account (1Post) | 20 |
The same table with sources is on the Kick specs page.
Good to know for Kick
A Kick post is a plain text chat line in your own channel. Kick also limits a message to 2,048 bytes in UTF-8, so text with many emoji or non-Latin letters can reach that before 500 characters.
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": "kick refuses this post: Kick counts 532 of 500 characters in part 1. (text_too_long).",
"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.