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

ActionWhyWhere to do itWhat the API offers
Campaign approvalA 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 → CampaignsCreate, update, cancel, results (createCampaign, updateCampaign, cancelCampaign)
Purchases and plan changesPayment approval has to stay with the user; card details don't pass through Hiboty.Creem payment pageRead plan and usage, management address (getBilling, getUsage)
Creating new API keysA key minting wider keys, or keys that survive its own revocation, would be a security hole.Dashboard → Settings → APIList and revoke (listApiKeys, revokeApiKey)
Passwords and 2FAAccount security can't be changed with an organization key; it belongs to the person.Dashboard → AccountNone
Personal account actionsName, email preferences, sessions, closing the account, creating an organization and notifications belong to the person, not the organization.Dashboard → AccountNone
Changing the four-eyes settingTurning off separation of duties on campaign approval shouldn't be possible with a leaked key.Dashboard → SettingsRead only (getOrganization, campaign_four_eyes)
Affiliate programCommission accounts and payout details (IBAN) belong to the person.Dashboard → Settings → AffiliateNone
One-click WhatsApp connection through FacebookMeta's approval popup needs a user session in a browser.Dashboard → Bot → ConnectionManual connection (connectBot)
Downloading all organization data in one fileIt extracts all personal data at once, so a signed-in admin has to start it.Dashboard → SettingsReading piece by piece (exportContacts, listAuditLogs, listOrders)
Deleting an organizationIt deletes all data irreversibly; it needs a signed-in owner's approval.Dashboard → SettingsRead and update settings (getOrganization, updateOrganization)
Ownership transferIt hands control of the organization to someone else.Dashboard → Settings → TeamRoles and bot access; the owner role can't be granted (updateTeamMember)
Stars refundsIt returns money to a customer and can't be undone.Dashboard → Mini App → OrdersRead 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.