hibikiDocsTechnical
For developers

Technical docs

Build on hibiki with REST APIs, OpenAPI, Bearer tokens, HMAC-signed webhooks, SDKs, and integration patterns for messaging, contacts, broadcasts, and campaigns.

Authentication

Use Bearer tokens for API requests. Keep tokens server-side and rotate them when a teammate or integration no longer needs access.

01
Create an API keySign in, open API keys, create a token, and store the raw token immediately.
02
Send the Authorization header"Authorization: Bearer " on every API request.
03
Scope by workspaceAPI activity follows the workspace behind the token.

Webhooks

Webhooks let your systems react to messages, broadcasts, campaign changes and delivery events.

01
Configure an endpointAdd your HTTPS endpoint and secret from the webhooks screen.
02
Verify HMAC signaturesReject payloads whose signature does not match the raw request body.
03
Make handlers idempotentDelivery retries can happen. Store event IDs before applying side effects.

Core resources

Most integrations start with contacts, conversations, messages, broadcasts, campaigns and webhook deliveries.

01
Contacts and listsSync CRM records, tags, custom fields and opt-in state.
02
Conversations and messagesRead inbound messages and send replies through connected channels.
03
Broadcasts and campaignsTrigger approved templates and connect downstream reporting.