Documentation

Akara API & Integrations

Connect Akara to your property-management stack. Let reservations create security-deposit requests automatically, and receive real-time events when a guest approves, disputes, or you release or claim a hold.

Quickstart

Create an API key and request your first deposit in a single POST.

API reference

Endpoints, authentication, webhook events, signatures, and errors.

Integrations

Native PMS & channel-manager connectors — what’s live and what’s coming.

How Akara fits in

Akara mediates security deposits: your PMS tells Akara a booking needs a deposit, the guest authorizes a card hold via the payment provider, and Akara coordinates the claim or release. Akara never holds guest funds — the authorization stays with the payment provider until you release or claim it.

  1. Your PMS → Akara. A reservation triggers a call to the inbound webhook, which creates a deposit request and emails the guest a secure link.
  2. Guest → Akara. The guest approves the hold on the deposit page. You can then release or claim it from your dashboard.
  3. Akara → Your server. Each state change fires a signed outbound webhook so your systems stay in sync.
Available today: the inbound webhook and outbound events work now with any system that can send an authenticated HTTP request. Native one-click PMS connectors are on the roadmap — see Integrations.