Pixelfed: posting rules and settings
What a Pixelfed channel accepts in Posty: media, limits, required fields, and the fields of the settings object for the API.
Basics
pixelfedPost types
The same channel accepts more than one kind of post, and each kind has different requirements. The table shows what you need for each.
| Type | Media | Notes |
|---|---|---|
| Picture post | 1 to 4 pictures | A post without a picture, or with a video, is refused. |
Rules
- Pixelfed has no platform-specific settings. The __type field is enough in the settings object.
- You connect the same way as on Mastodon: you type the address of your server, Posty registers itself there, and you sign in as usual.
- A post without a picture is refused, and so is a post with a video.
- The limits are the Pixelfed defaults (500 caption characters, 4 pictures). A server admin can change them.
Settings fields
The settings object only needs the __type field. The editor does not show a separate settings section for this channel.
Examples
Each example is one item in the POST /public/v1/posts request's posts array. The envelope around it is always this:
{
"type": "schedule",
"date": "2026-09-15T09:00:00.000Z",
"shortLink": false,
"posts": [ /* the item below */ ]
}Picture post
The settings object only needs the __type field.
{
"integration": { "id": "<pixelfed-channel>" },
"value": [{
"content": "<p>Morning light at the lake.</p>",
"image": [{ "id": "<media>", "path": "https://uploads.posty.hu/lake.jpg" }]
}],
"settings": { "__type": "pixelfed" }
}The channel ID comes from the channel list, and the path values for images and videos from media upload. The exact schema for the connected account comes from the settings schema endpoint. From the command line, the same thing is the --settings flag. See the CLI examples.