Overview

Base URL

All public API requests go to:

https://api.kirisan.com

Use this host in production. Local development may use a different base URL configured in the dashboard — production integrations should always target https://api.kirisan.com.

Authentication

Every request requires your account API token:

Authorization: Bearer YOUR_ACCOUNT_TOKEN

Copy the token from Account → Settings in the dashboard. See Authentication for channel keys and token rotation.

Available endpoints

Method	Path	Purpose
POST	/v1/send	Send to one recipient (optionally on multiple channels)

There is no separate public bulk-send endpoint. For large batches use Send → Campaign in the dashboard, or call POST /v1/send once per recipient from your application.

Create and manage message templates in the dashboard under Channel → channel → Templates. Use a template ID in the send body, or pass inline message content — see Send API.

Response format

Successful responses include "status": true.

Errors include "status": false and a "reason" string. HTTP status is 401/403 for auth problems; many validation errors use 400. See Errors for the full list.

POST /v1/send adds a "channels" object with per-channel results:

{
  "status": true,
  "channels": {
    "whatsapp": { "status": true, "processing_time": "120ms" }
  }
}

Scheduled sends also include "scheduled": true at the top level and on each channel.

Typical integration flow

1. Copy your account token from Account → Settings.
2. Copy channel keys (device or sender tokens) from the relevant Channel → … page.
3. Build content with inline messages, or reference a template ID from the dashboard.
4. Call POST /v1/send with keys, content, and target.
5. Read "status" and each entry under "channels" — reasons for failures are per channel.

The dashboard Send screen uses the same /v1/send endpoint, so API behavior matches what you see in the UI.

Related

• Authentication — account token and channel keys
• Send API — full request body reference
• Webhook overview — inbound POST payloads to your server
• Errors — status codes and common reasons
• Send messages — compose sends in the dashboard