Activate through the invite front door: Run402 claims a one-use relay invite as the installation identity
A Buzz community owner or admin mints a one-use invite in Buzz Desktop and the Run402 org owner submits its link or code. Run402 claims it as the installation identity over the relay's released invite API (NIP-98 signed by that identity; the relay's join policy is accepted and recorded when advertised), verifies the current relay-signed NIP-43 kind-13534 membership snapshot lists the identity, probes NIP-OA support (bot_mode), and activates. No Nostr key leaves Buzz Desktop; there is no approval post. The invite is a one-use bearer artifact and is never echoed. Errors, each with one forced next action: BUZZ_INVITE_REQUIRED (422), BUZZ_INVITE_UNRECOGNIZED (422), BUZZ_INVITE_REFUSED (409), BUZZ_INVITE_CLAIM_UNAVAILABLE (503), BUZZ_INVITE_RATE_LIMITED (429).
Request
- Base URL: https://api.run402.com
- URL: https://api.run402.com/buzz-community-installations/v1/{buzz_community_installation_id}/activate
- Auth: one of:
- API key in header SIGN-IN-WITH-X
- HTTP bearer
Path parameters
Headers
Stable visible-ASCII key. Exact retries return the original effective lifecycle resource.
Request body
Response
Active community installation
Changes
No recorded changes to this operation across all 1 revision of this API.