Nostr Event Publish Schedule

Schedule nostr events for future publishing

Schedule events to be published in the future. (Job requests can be encrypted per NIP-90.) Events to be published can have a different pubkey than the requester’s pubkey (i.e. an event can be scheduled to be published by a different user than the user who scheduling it).

Input

Event(s) to be scheduled

[ "i", "<stringified-event-json", "text" ]

Params

  • relays - array of relays to publish to (optional)

Output

Event ID that was published.

Feedback

Job feedback is sent back the moment an event is scheduled.

{
    "content": nip04_encrypt("
        [ \"status\", \"success\", \"Job has been scheduled, you can manage it on <....>\" ]
    "),
    "kind": 7000,
    "tags": [
        [ "e", "<5905-event-job-request>" ],
        [ "p", "<pubkey-a>" ],
        [ "encrypted" ]
    ]
}

Example

Request

{
    "content": nip04_encrypt("
        [ \"i\", \"<stringified-event-json>\", \"text\" ],
        [ \"param\", \"relays\", \"wss://nos.lol\", \"wss://relay.damus.social\" ]
    "),
    "kind": 5905,
    "pubkey": "<pubkey-a>",
    "tags": [
        [ "p", "<dvm-pubkey>" ],
        [ "encrypted" ]
    ]
}

Feedback

A feedback

Desponse

{
    "content": "<eventid-of-1040-event>",
    "kind": 6900,
    "tags": [
        [ "p", "<pubkey-a>" ],
        [ "e", "<event-id-of-5900>" ]
    ]
}