Developers
Deliberately not in the API
These aren't gaps: they stay in the dashboard or on the payment page so that a leaked key or a misdirected assistant can't do them.
Actions that stay in the dashboard
| Action | Why | Where to do it | What the API offers |
|---|---|---|---|
| Campaign approval | A mass send can't be undone; the four-eyes rule needs a person to see the content and approve it. A change made with a key needs approval again. | Dashboard → Campaigns | Create, update, cancel, results (createCampaign, updateCampaign, cancelCampaign) |
| Purchases and plan changes | Payment approval has to stay with the user; card details don't pass through Hiboty. | Creem payment page | Read plan and usage, management address (getBilling, getUsage) |
| Creating new API keys | A key minting wider keys, or keys that survive its own revocation, would be a security hole. | Dashboard → Settings → API | List and revoke (listApiKeys, revokeApiKey) |
| Passwords and 2FA | Account security can't be changed with an organization key; it belongs to the person. | Dashboard → Account | None |
| Personal account actions | Name, email preferences, sessions, closing the account, creating an organization and notifications belong to the person, not the organization. | Dashboard → Account | None |
| Changing the four-eyes setting | Turning off separation of duties on campaign approval shouldn't be possible with a leaked key. | Dashboard → Settings | Read only (getOrganization, campaign_four_eyes) |
| Affiliate program | Commission accounts and payout details (IBAN) belong to the person. | Dashboard → Settings → Affiliate | None |
| One-click WhatsApp connection through Facebook | Meta's approval popup needs a user session in a browser. | Dashboard → Bot → Connection | Manual connection (connectBot) |
| Downloading all organization data in one file | It extracts all personal data at once, so a signed-in admin has to start it. | Dashboard → Settings | Reading piece by piece (exportContacts, listAuditLogs, listOrders) |
| Deleting an organization | It deletes all data irreversibly; it needs a signed-in owner's approval. | Dashboard → Settings | Read and update settings (getOrganization, updateOrganization) |
| Ownership transfer | It hands control of the organization to someone else. | Dashboard → Settings → Team | Roles and bot access; the owner role can't be granted (updateTeamMember) |
| Stars refunds | It returns money to a customer and can't be undone. | Dashboard → Mini App → Orders | Read orders and change their status (listOrders, updateOrder) |
Values that are never returned
Tokens, API keys, webhook signing secrets and AI provider keys are never returned in a response, apart from those issued at creation; only status details such as connected come back. The samples in these docs contain no real secrets: hb_live_YOUR_API_KEY and $HIBOTY_API_KEY are placeholders.