Participation workflows

Use the workflow endpoints to let an account take part in a resource (RSVP to an event, enroll in a course or quest, apply for a job) and to let organizers review those participants. This page covers the rules every workflow shares and the event endpoints. Courses and jobs are on Course and job workflows; quests are on Quest workflows.

All endpoints are under https://app.hive3.tech/api/v1, authenticate with an API key (see authentication) and use the response envelope from Requests, errors and limits. API access needs Honey Bee or above; see the developer overview. Some field names (personId, communityId) predate unified accounts and identify accounts: the API calls an account that others join a community. Examples that read no body from you show only curl; JavaScript and Python follow the pattern of the first example below.

#Shared rules

#Access decisions

Participant requests (RSVP, enroll, complete a lesson, apply) use the same live access decision as the Hive3 web app, so the result can change without a new key:

• A members-only resource needs an accepted membership in the owning community.
• A paid resource needs the matching subscription plan or a purchased ticket.
• Managers of the resource are exempt.

A denied request returns 403 forbidden with a resource-specific message (for example You cannot RSVP for this event). Withdrawing ({ "enroll": false }) skips the access decision, but a declined participant still gets 409 conflict.

#Managers and participants

Participant routes act as the key owner and need resources:write. Manager routes list participants and record decisions. They need resources:read (lists) or resources:write (changes) and a current owner, admin or moderator role on the account that owns the resource; anyone else gets 403 forbidden (You cannot manage this event). Managing another account's resource also needs communities:read (lists) or communities:write (changes), otherwise 403 insufficient_scope with requiredScopes. See the role matrix.

If the key is limited to selected accounts, every workflow route on a resource owned by an account outside that list returns 403 forbidden (API key does not include this community).

Manager lists include each participant's email next to personId, name, username and image. Treat them as personal data.

#Declined participants and capacity

• After an organizer declines a participant (accepted: false), that participant's join or leave request returns 409 conflict (Enrollment was declined by the organizer. Contact the organizer to change this decision.). Only an organizer can change the decision.
• Joining a full event or course returns 400 invalid_request with the capacity message (Sorry, this event is at full capacity.).
• accepted is true when the participant is approved, null when the organizer must still decide (the resource has automatic enrollment turned off) and false when declined.

#Limits

Manager lists return at most 200 rows and have no page object. POST workflow requests are limited to 60 per minute per account and domain (events, courses, quests, jobs), PATCH to 120 per minute; a request over the limit returns 429 rate_limited with a Retry-After header. Request bodies are limited to 128 KB. The 600 requests per minute account budget is in Rate limits.

#Attachment objects

Quest evidence and job applications take files as attachment objects:

fileName, contentType and byteSize are required even when you send a url. For a storageId, the stored file's real type and size are checked as well.

#Events

An event RSVP is the participant record for an event. Use these endpoints to RSVP on behalf of the key owner and to let organizers approve RSVPs and record attendance.

curl https://app.hive3.tech/api/v1/workflows/events/event_123/participants \
  -H "Authorization: Bearer $HIVE_API_KEY"

const res = await fetch("https://app.hive3.tech/api/v1/workflows/events/event_123/participants", {
  headers: { Authorization: `Bearer ${process.env.HIVE_API_KEY}` },
});
const { data } = await res.json();

import os
import requests

res = requests.get(
    "https://app.hive3.tech/api/v1/workflows/events/event_123/participants",
    headers={"Authorization": f"Bearer {os.environ['HIVE_API_KEY']}"},
)
data = res.json()["data"]

{
  "data": [
    {
      "personId": "account_456",
      "name": "Ada Lovelace",
      "email": "ada@example.com",
      "username": "ada",
      "image": "https://example.com/ada.png",
      "enrollmentId": "enrollment_789",
      "accepted": true,
      "enrolledAt": "2026-10-20T09:30:00.000Z",
      "attendedAt": "2026-10-27T18:02:11.000Z",
      "resolvedWallet": "0x0000000000000000000000000000000000000001",
      "whitelisted": false
    }
  ]
}

curl -X POST https://app.hive3.tech/api/v1/workflows/events/event_123/rsvp \
  -H "Authorization: Bearer $HIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"enroll": true}'

const res = await fetch("https://app.hive3.tech/api/v1/workflows/events/event_123/rsvp", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.HIVE_API_KEY}`, "Content-Type": "application/json" },
  body: JSON.stringify({ enroll: true }),
});
const { data } = await res.json();

import os
import requests

res = requests.post(
    "https://app.hive3.tech/api/v1/workflows/events/event_123/rsvp",
    headers={"Authorization": f"Bearer {os.environ['HIVE_API_KEY']}"},
    json={"enroll": True},
)
data = res.json()["data"]

{
  "data": {
    "eventId": "event_123",
    "enrollmentId": "enrollment_789",
    "accepted": null,
    "isRSVPd": true
  }
}

curl -X PATCH https://app.hive3.tech/api/v1/workflows/events/event_123/participants/enrollment_789 \
  -H "Authorization: Bearer $HIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"accepted": true}'

const res = await fetch("https://app.hive3.tech/api/v1/workflows/events/event_123/participants/enrollment_789", {
  method: "PATCH",
  headers: { Authorization: `Bearer ${process.env.HIVE_API_KEY}`, "Content-Type": "application/json" },
  body: JSON.stringify({ accepted: true }),
});
const { data } = await res.json();

import os
import requests

res = requests.patch(
    "https://app.hive3.tech/api/v1/workflows/events/event_123/participants/enrollment_789",
    headers={"Authorization": f"Bearer {os.environ['HIVE_API_KEY']}"},
    json={"accepted": True},
)
data = res.json()["data"]

{ "data": { "enrollmentId": "enrollment_789", "updated": true } }

curl -X POST https://app.hive3.tech/api/v1/workflows/events/event_123/attendance \
  -H "Authorization: Bearer $HIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"enrollmentId": "enrollment_789"}'

const res = await fetch("https://app.hive3.tech/api/v1/workflows/events/event_123/attendance", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.HIVE_API_KEY}`, "Content-Type": "application/json" },
  body: JSON.stringify({ enrollmentId: "enrollment_789" }),
});
const { data } = await res.json();

import os
import requests

res = requests.post(
    "https://app.hive3.tech/api/v1/workflows/events/event_123/attendance",
    headers={"Authorization": f"Bearer {os.environ['HIVE_API_KEY']}"},
    json={"enrollmentId": "enrollment_789"},
)
data = res.json()["data"]

{ "data": { "enrollmentId": "enrollment_789", "updated": true } }