Nostr: posting rules and settings

What a Nostr channel accepts in Postemi: media, limits, required fields, and the fields of the settings object for the API.

Basics

Rules

• Nostr has no platform-specific settings. The __type field is enough in the settings object.
• You connect with your private key (nsec1... or 64 hex characters). Postemi stores it encrypted. A Nostr key cannot be revoked, so only use one you are fine sharing.
• Each note goes to relay.damus.io, nos.lol, relay.primal.net, relay.snort.social and offchain.pub. It counts as published when one relay confirms it.
• Extra parts of a post are published as replies to it, in order.
• Beta: not yet tested with many accounts.

Settings fields

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 */ ]
}

{
  "integration": { "id": "<channel-id>" },
  "value": [{ "content": "<p>The text of the post.</p>", "image": [] }],
  "settings": { "__type": "nostr" }
}

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.