These five commands arrived in CLI version 0.4, so every command and flag on this page is (0.4+). If hive3 search prints Unknown command: search, your installed CLI is older; run hive3 update --check. Shared conventions such as output, exit codes, --file and --account are on the main CLI command reference.
Keys created before the broadcast, ticket, AI and credential scopes existed do not include them. Sign in again with hive3 login to get a key that does. Search uses the existing resources:read scope. When you target another account with --account, each command also needs communities:read (reads) or communities:write (writes) and your current role. See Act on another account.
#Search
| Command | What it does | Flags | Scopes |
|---|---|---|---|
hive3 search <query> | Searches accounts, events, courses, content, quests and jobs that your account can see. | --type <type>, --limit <n>, --cursor <cursor> | resources:read |
--typeisall(default),accounts,events,courses,content,questsorjobs.--limitis a whole number from 1 to 50 (default 20).- The query is 1 to 100 characters. Several words are joined with spaces, so quotes are optional; use them to stop your shell from splitting special characters.
- Each result has a
type(account,event, and so on) and anid. Use--cursorwith thenextCursorof the previous response to read more.
hive3 search "design guild" --type accounts --limit 10
hive3 search portfolio night --type events#Broadcasts
Broadcasts are emails to an account's opted-in members. You must be owner, admin or moderator of the account. See Broadcasts for the API and Email broadcasts for the app.
| Command | What it does | Flags | Scopes |
|---|---|---|---|
hive3 broadcasts list | Lists broadcasts, newest first. | --account, --limit <n>, --cursor <cursor> | broadcasts:read |
hive3 broadcasts audience | Shows the recipient count and when you may send next. | --account | broadcasts:read |
hive3 broadcasts get <id> | Reads one broadcast, including its text and HTML. | None | broadcasts:read |
hive3 broadcasts create | Creates a draft. | --subject <text>, --body-text <text> (both required, directly or in the file), --body-html <html>, --body-mode <mode>, --hero-image-url <url>, --file <path>, --idempotency-key <key>, --account | broadcasts:write |
hive3 broadcasts update <id> | Changes a draft. At least one field is required. | --subject, --body-text, --body-html, --body-mode, --hero-image-url <url>, --remove-hero-image, --file <path> | broadcasts:write |
hive3 broadcasts test <id> | Emails the draft to your own primary address only. | None | broadcasts:write |
hive3 broadcasts send <id> | Emails every opted-in member now, or schedules the send. | --yes (required), --at <date-time> | broadcasts:write |
hive3 broadcasts cancel <id> | Returns a scheduled broadcast to draft. | None | broadcasts:write |
--body-modeiseditor(default) orhtml.--body-htmlis cleaned the same way as in the app editor; without it, HTML is built from the paragraphs of--body-text.--subjectis 1 to 180 characters.--hero-image-urlmust be anhttporhttpsURL.--remove-hero-imageclears the image and cannot be combined with--hero-image-url.- With
--file, the file is read first and flags override it. The file usessubject,bodyText,bodyHtml,bodyModeandheroImageUrl. - Only drafts can be edited. There is no delete. A send reaches at most 5,000 opted-in accepted members.
sendrequires--yesbecause an immediate send cannot be undone once it starts.--attakes an ISO 8601 date-time such as2026-12-01T15:00:00Zfrom 1 minute to 90 days ahead;cancelundoes a scheduled send.- How often you can send depends on the plan: Honey Bee every 30 days, Swarm every 14, Royal Hive every 7. Worker Bee cannot send.
broadcasts audienceshows when the next send is allowed. createallows 30 writes per minute, andtest10 per hour.
{
"subject": "November news",
"bodyText": "Portfolio night is back.\n\nSee you on the 12th."
}hive3 broadcasts audience --account design-guild
hive3 broadcasts create --file broadcast.json --account design-guild --idempotency-key november-news
hive3 broadcasts test "<broadcast-id>"
hive3 broadcasts send "<broadcast-id>" --yes --at 2026-11-02T15:00:00Z
hive3 broadcasts cancel "<broadcast-id>"#Tickets
Tickets are the paid entries set up on an account's events, courses and quests. Creating tickets, checkout and refunds are not available from the CLI.
| Command | What it does | Flags | Scopes |
|---|---|---|---|
hive3 tickets list | Lists tickets an account sells. Owners and admins only. | --account, --limit <n>, --cursor <cursor> | tickets:read |
hive3 tickets get <id> | Reads one ticket. | None | tickets:read |
hive3 tickets update <id> | Changes a ticket. At least one field is required. | --name <text>, --description <text>, --amount <amount>, --currency <code>, --status <status> | tickets:write |
hive3 tickets mine | Lists tickets you bought, with their status. | --limit <n>, --cursor <cursor> | tickets:read |
--amountis a positive decimal with at most two decimals, such as12.50.--currencyis a three-letter code, such asUSD; it is converted to upper case.--statusisactiveorinactive. Turning a ticket back on needs a seller on Honey Bee or above.- Managing tickets is for owners and admins; moderators cannot.
hive3 tickets list --account design-guild
hive3 tickets update "<ticket-id>" --amount 12.50 --currency USD
hive3 tickets update "<ticket-id>" --status inactive#AI assistant
Each account can have one assistant that answers questions from documents you provide. It needs a Honey Bee or higher account, and the first update creates it. Chatting with the assistant is not available from the CLI. See AI assistant for the app.
| Command | What it does | Flags | Scopes |
|---|---|---|---|
hive3 assistant get | Reads the assistant. Before the first save it returns defaults. | --account | ai:read |
hive3 assistant update | Changes the assistant. At least one field is required. | --name <text>, --description <text>, --avatar-url <url>, --visibility <value>, --account | ai:write |
hive3 assistant documents | Lists training documents. documents list is the same. | --account | ai:read |
hive3 assistant documents add <file> | Uploads a file and attaches it, in one step. | --content-type <mime>, --idempotency-key <key>, --account | ai:write |
hive3 assistant documents delete <document-id> | Removes a document and its stored file. | --confirm <document-id> (required) | ai:write |
--visibilityispublic,protectedorprivate. The name is 1 to 80 characters and the description up to 2,000.- Documents are PDF, DOCX or plain text up to 5 MB, and up to 50 per assistant. The CLI infers the type from
.pdf,.docxand.txt; pass--content-typefor other extensions. A file over the limit is refused before it is uploaded, and the upload address is checked the same way as inhive3 upload. - The assistant is limited to 20 saves per minute.
hive3 assistant update --name "Guild helper" --description "Answers member questions" --visibility private
hive3 assistant documents add ./faq.pdf
hive3 assistant documents
hive3 assistant documents delete "<document-id>" --confirm "<document-id>"#Credentials
You can read credentials and award custom ones. Creating, editing, minting, deploying and claiming credentials are not available from the CLI; claiming happens in the app. See Create and award credentials.
| Command | What it does | Flags | Scopes |
|---|---|---|---|
hive3 credentials list | Lists credentials an account issues. | --account, --limit <n>, --cursor <cursor> | credentials:read |
hive3 credentials get <id> | Reads one credential you manage, or one whose owner's activity you can see. | None | credentials:read |
hive3 credentials award <id> | Awards a custom credential to people by handle. | --handles <list> (required), --yes (required) | credentials:write |
hive3 credentials mine | Lists credentials you have claimed, with status. | None | credentials:read |
hive3 credentials claimable | Lists credentials awarded to you and not yet claimed. | --limit <n>, --cursor <cursor> | credentials:read |
--handlesis a comma-separated list of 1 to 50 handles. A leading@is allowed:@alice,bob.- Only custom (general) credentials can be awarded. People who already hold the award are skipped and not notified again, so repeating the command is safe. The response has
awardedandnotFound. awardrequires--yesbecause it cannot be undone through the CLI.- Awarding needs owner, admin or moderator on the credential's account.
hive3 credentials list --account design-guild
hive3 credentials award "<credential-id>" --handles @alice,bob --yes
hive3 credentials claimable