Events, courses, content, quests and jobs

Use these endpoints to publish and maintain the things people join in Hive3: events, courses, content, quests and jobs. You can sync a catalog from another system, schedule events from a calendar, post jobs from an applicant tracker, or let an AI agent draft and publish for a community you help run. All five kinds share one set of operations, described here. Course and content fields, event scheduling and world booking, and quest credits have their own pages: Courses and content, Events: slots and worlds and Quests: credits and objectives. To enroll, RSVP, apply or review participants, see Participation workflows.

API access needs a Honey Bee plan or above; see the developer overview. The examples read the key from HIVE_API_KEY. Operations shown with one curl block follow the same pattern in JavaScript (fetch) and Python (requests) as the full examples. Some field names still say community or person; both identify accounts, and a "community" is an account that others join.

#Kinds and scopes

The path segment {kind} is one of events, courses, content, quests or jobs. Posts use the same shape on their own page.

For a community you manage, the key owner must currently be an owner, admin or moderator of it, and the key's account allowlist (if set) must include it; see Managed accounts. Reads return only resources owned by your account or by accounts you manage; other accounts' public resources return 404. Use Search to find them.

#Shared behavior

• Owner. Create for your own account by omitting owner (or { "type": "person" }). To create for a community, send { "owner": { "type": "community", "communityId": "account_456" } } (an account ID or @handle). Any other owner value is ignored. owner is ignored on update.
• Visibility. public (default), protected (members only) or private; unknown values become public. A Worker Bee owning account can only publish public resources: a request that newly sets another value returns 403 forbidden (A Honey Bee subscription is required to make content members-only or private), and one that newly sets a subscriptionId returns 403 forbidden (A Honey Bee subscription is required to sell subscriptions, tickets or paid access). The owning account's plan decides, not the acting admin's. Values a resource already stores can stay after a downgrade.
• Subscriptions. subscriptionId ties access to one of the owning account's subscription plans. Moderators can only choose an existing plan of that account (403 forbidden, Choose an existing subscription plan of this account).
• Title and description. title (or name) is required on create (400, Title is required). description also accepts shortDescription and body.
• Images and files. URL fields (imageUrl, heroImage, attachmentUrl) take plain URLs. *StorageId fields (imageStorageId, heroImageStorageId, attachmentStorageId, employerLogoStorageId) take upload IDs from Uploads made by the same key owner. Image fields need an image upload; a bad ID returns 400 invalid_request (imageStorageId must be a valid storage ID) or 404 not_found.
• Other fields. For events, courses, content and quests the whole JSON body is kept in the response's data object, so unknown fields are stored as sent. Jobs keep only the fields listed below.
• Server-owned fields. The server sets id, type, owner, createdAt, updatedAt and archivedAt. Each kind also protects a few fields (event metaverseTime, courseId, kind, officeHours and sessionKey; quest maxQuestDays, questCreditSource, questCreditId) and ignores values you send for them.
• Timestamps. Resource timestamps in responses are epoch milliseconds. Schedule fields you send are ISO 8601 strings; events require an offset or Z (Timestamps).
• Updates. PATCH is partial: omitted fields keep their value. Arrays you send (eventSlots, lessons, objectives, sections, tags, badges) replace the stored array.
• Archiving. DELETE archives; archived resources disappear from lists, reads and search and cannot be updated (404).

All kinds allow 60 creates per minute, 120 updates per minute and 60 archives per minute per account, on top of the account's 600 requests per minute. A body above its size limit (measured on the serialized request) returns 400 invalid_request (<kind> payload is too large), or 413 when the raw body is more than 4 KiB over it. Limited requests return 429 rate_limited with Retry-After.

#List and read resources

curl "https://app.hive3.tech/api/v1/jobs?limit=2" \
  -H "Authorization: Bearer $HIVE_API_KEY"

const res = await fetch("https://app.hive3.tech/api/v1/jobs?limit=2", {
  headers: { Authorization: `Bearer ${process.env.HIVE_API_KEY}` },
});
const { data, page } = await res.json();

import os, requests

res = requests.get(
    "https://app.hive3.tech/api/v1/jobs",
    params={"limit": 2},
    headers={"Authorization": f"Bearer {os.environ['HIVE_API_KEY']}"},
)
jobs = res.json()["data"]

{
  "data": [
    {
      "id": "job_123",
      "type": "job",
      "title": "Community Manager",
      "description": "Grow and support our member community.",
      "employerName": "Design Guild",
      "employmentType": "full-time",
      "location": "Remote",
      "status": "published",
      "visibility": "public",
      "badges": [],
      "owner": { "type": "person", "personId": "account_123" },
      "createdAt": 1767225600000,
      "updatedAt": 1767225600000
    }
  ],
  "page": { "nextCursor": null, "hasMore": false }
}

curl https://app.hive3.tech/api/v1/jobs/job_123 \
  -H "Authorization: Bearer $HIVE_API_KEY"

#Create a resource

curl -X POST https://app.hive3.tech/api/v1/jobs \
  -H "Authorization: Bearer $HIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: job-community-manager-001" \
  -d '{"title":"Community Manager","description":"Grow and support our member community.","employerName":"Design Guild","employmentType":"full-time","location":"Remote"}'

const res = await fetch("https://app.hive3.tech/api/v1/jobs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.HIVE_API_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": "job-community-manager-001",
  },
  body: JSON.stringify({
    title: "Community Manager",
    description: "Grow and support our member community.",
    employerName: "Design Guild",
    employmentType: "full-time",
    location: "Remote",
  }),
});
const { data } = await res.json();

import os, requests

res = requests.post(
    "https://app.hive3.tech/api/v1/jobs",
    headers={
        "Authorization": f"Bearer {os.environ['HIVE_API_KEY']}",
        "Idempotency-Key": "job-community-manager-001",
    },
    json={
        "title": "Community Manager",
        "description": "Grow and support our member community.",
        "employerName": "Design Guild",
        "employmentType": "full-time",
        "location": "Remote",
    },
)
job = res.json()["data"]

{
  "data": {
    "id": "job_123",
    "type": "job",
    "title": "Community Manager",
    "description": "Grow and support our member community.",
    "employerName": "Design Guild",
    "employmentType": "full-time",
    "location": "Remote",
    "status": "published",
    "visibility": "public",
    "badges": [],
    "owner": { "type": "person", "personId": "account_123" },
    "createdAt": 1767225600000,
    "updatedAt": 1767225600000
  }
}

#Update and archive

curl -X PATCH https://app.hive3.tech/api/v1/jobs/job_123 \
  -H "Authorization: Bearer $HIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"location":"Remote (Europe)","payRangeMin":"60000","payRangeMax":"80000"}'

curl -X DELETE https://app.hive3.tech/api/v1/jobs/job_123 \
  -H "Authorization: Bearer $HIVE_API_KEY"

#Job fields

Jobs keep only the fields below; others are dropped. Courses, content, events and quests have their own field lists on the pages linked at the end.

#Fields for the other kinds

Courses, content, events and quests take more fields than the common ones above:

• Courses and content have lessons, office hours, sections and tags. See Courses and content.
• Events take eventSlots (each with ISO 8601 startsAt and endsAt), autoEnroll (default false) and an optional worldId. See Events: slots and worlds.
• Quests need a questCreditPlan (single or bundle) that spends one quest credit, plus objectives, startsAt and endsAt. See Quests: credits and objectives.