This Cloudflare worker exposes a HTTP interface to publish events to specified Nostr relays. The HTTP request is non-blocking and will immediatelly return. The events will be published asynchronously.

The goal of this worker is to make it easier to integrate publishing events into any application. Using this worker applications do not need to integrate websockets and can publish events through a non-blocking HTTP request.

Send a JSON body with the the event and the relays that the event should be published to.

{
  "relays": ["relay.damus.io", "relay.snort.social"],
  "event": { JSON of the EVENT }
}

The HTTP request will immediatelly return and the the events are published asynchonously.

Retrieve the profile for a pubkey.

{
  "relays": ["relay.damus.io", "relay.snort.social"],
  "pubkey": "profile-pubkey"
}

If a profile is already cached it will return with HTTP status 200.

If a profile is NOT already cached it will return with HTTP status 202 and query the profile asynchronously.

The profile data is cached in a worker KV (a global, low-latency, key-value data store).

Configure the KV:

$ wrangler kv:namespace create PROFILES
$ wrangler kv:namespace create PROFILES --preview

and add the kv_namespaces array to the wrangler.toml

To protect your worker you can set a API_TOKEN environment variable.

Clients then need to send this token in a API-TOKEN HTTP header.

Refer to the Cloudflare docs Learn more about Cloudflare workers and how to publish workers

$ wrangler publish

$ wrangler dev