⚙️ Setup & Administration

API, Bearer tokens and webhooks

Connect Ohana360 to other systems: API token generation, REST endpoints and HMAC-signed webhook notifications.

API tokens

Generate access keys for your org on the Setup > API Tokens screen. A token is used with the Authorization: Bearer <token> request header.

Tokens belong to the org and can be revoked at any time.
Generate a separate token per integration; a revoke then cuts only that connection.

Security: A token is a password: never put it in a code repository, an e-mail or a screenshot. If you suspect a leak, revoke immediately and generate a new one.

Data access over REST

Read, create and update records over the API. Typical uses:

Writing invoice status into Ohana360 from your accounting software
Creating records directly from a custom form on your site
Pulling data into an external reporting tool

Webhooks

Define a URL under Setup > Webhooks; when records are created or changed on the objects you chose, Ohana360 sends a JSON notification to that address.

Every notification carries an HMAC signature in the X-Ohana-Signature header: the receiver verifies the request truly came from Ohana360.
Undelivered notifications are retried from a queue.
Example: opening an order in your ERP when an opportunity becomes Won.

Calling webhooks from flows

Webhooks can also be triggered as a flow action: build your conditions in the flow and wake the external system only when needed.

Tip: When starting an integration, verify the end-to-end flow with a single test record first; enable bulk sync later.