Accounts

Overview

Accounts represent your WhatsApp Business API connections. Each account is linked to a phone number (phone_id) registered under a WhatsApp Business Account (business_id) on Meta’s WhatsApp Business Platform.

Note

For security, account responses never return the raw access_token or app_secret. They expose boolean presence flags (has_access_token, has_app_secret) instead. Secrets are AES-encrypted at rest.

List Accounts

Retrieve all connected WhatsApp accounts for the organization.

GET /api/accounts

Response

{
  "status": "success",
  "data": {
    "accounts": [
      {
        "id": "uuid",
        "name": "Main Business",
        "app_id": "1234567890",
        "phone_id": "123456789",
        "business_id": "987654321",
        "api_version": "v21.0",
        "is_default_incoming": true,
        "is_default_outgoing": true,
        "auto_read_receipt": false,
        "business_calling_enabled": false,
        "status": "active",
        "has_access_token": true,
        "has_app_secret": true,
        "phone_number": "+1234567890",
        "display_name": "Main Business",
        "created_by_name": "Admin User",
        "created_at": "2024-01-01T00:00:00Z",
        "updated_at": "2024-01-01T00:00:00Z"
      }
    ]
  }
}

Note

The list response is a bare { "accounts": [...] } object — it does not include total, page, or limit pagination fields.

Get Account

Retrieve a single account.

GET /api/accounts/{id}

Response

{
  "status": "success",
  "data": {
    "id": "uuid",
    "name": "Main Business",
    "app_id": "1234567890",
    "phone_id": "123456789",
    "business_id": "987654321",
    "webhook_verify_token": "your_verify_token",
    "api_version": "v21.0",
    "is_default_incoming": true,
    "is_default_outgoing": true,
    "auto_read_receipt": false,
    "business_calling_enabled": false,
    "status": "active",
    "has_access_token": true,
    "has_app_secret": true,
    "phone_number": "+1234567890",
    "display_name": "Main Business",
    "created_by_id": "uuid",
    "created_by_name": "Admin User",
    "updated_by_id": "uuid",
    "updated_by_name": "Admin User",
    "created_at": "2024-01-01T00:00:00Z",
    "updated_at": "2024-01-01T00:00:00Z"
  }
}

Response Fields

Field	Type	Description
phone_id	string	Meta phone number ID
business_id	string	WhatsApp Business Account (WABA) ID
has_access_token	boolean	Whether an access token is stored (the token itself is never returned)
has_app_secret	boolean	Whether a Meta App Secret is stored
phone_number	string	The display phone number, when available
display_name	string	Verified display name, when available
status	string	Account status (see table below)
created_by_name / updated_by_name	string	Names of the users who created/last updated the account

Create Account

Connect a new WhatsApp Business account manually.

POST /api/accounts

Request Body

{
  "name": "Support Line",
  "phone_id": "123456789",
  "business_id": "987654321",
  "access_token": "EAAxxxx...",
  "app_id": "1234567890",
  "app_secret": "your_meta_app_secret",
  "api_version": "v21.0",
  "webhook_verify_token": "your_custom_verify_token",
  "is_default_incoming": false,
  "is_default_outgoing": false,
  "auto_read_receipt": false,
  "business_calling_enabled": false
}

Request Fields

Field	Type	Required	Description
name	string	Yes	Human-readable account name
phone_id	string	Yes	Meta phone number ID
business_id	string	Yes	WhatsApp Business Account (WABA) ID
access_token	string	Yes	Meta access token (stored encrypted)
app_id	string	No	Meta App ID
app_secret	string	No	Meta App Secret for webhook signature verification (stored encrypted)
webhook_verify_token	string	No	Verify token; auto-generated if omitted
api_version	string	No	Graph API version; defaults to the server default (e.g. v21.0)
is_default_incoming	boolean	No	Use this account as the default for incoming messages
is_default_outgoing	boolean	No	Use this account as the default for outgoing messages
auto_read_receipt	boolean	No	Automatically send read receipts for incoming messages
business_calling_enabled	boolean	No	Enrolled in the Business Calling API (required to send Call buttons)

Response

Returns the created account in the same shape as Get Account.

Update Account

Update account settings. Send only the fields you want to change; omitted string fields are left unchanged.

PUT /api/accounts/{id}

Request Body

{
  "name": "Customer Support",
  "access_token": "EAAyyyy...",
  "auto_read_receipt": true
}

Delete Account

Remove a WhatsApp account connection.

DELETE /api/accounts/{id}

Response

{
  "status": "success",
  "data": {
    "message": "Account deleted successfully"
  }
}

Caution

Deleting an account will remove all associated contacts, messages, and settings.

Test Connection

Verify the account credentials against Meta and fetch live phone details.

POST /api/accounts/{id}/test

Response

{
  "status": "success",
  "data": {
    "success": true,
    "display_phone_number": "(123) 456-7890",
    "verified_name": "Your Business Name",
    "quality_rating": "GREEN",
    "messaging_limit_tier": "TIER_1K",
    "code_verification_status": "VERIFIED",
    "account_mode": "LIVE",
    "is_test_number": false
  }
}

Note

quality_rating and messaging_limit_tier are live values fetched from Meta by the test endpoint — they are not persisted fields on the account record.

Register Phone Number

Register the phone number with Meta and set a two-step verification PIN. Used to complete manual or embedded-signup setup. A random 6-digit PIN is generated if none is supplied. SMB (Business App) numbers are already registered and skip this step.

POST /api/accounts/{id}/register

Request Body

{
  "pin": "123456"
}

Response

{
  "status": "success",
  "data": {
    "success": true,
    "message": "Phone number registered successfully",
    "pin": "123456"
  }
}

Subscribe App to Webhooks

Subscribe the app to webhooks for the account’s WhatsApp Business Account. Required after registration to start receiving incoming messages.

POST /api/accounts/{id}/subscribe

Response

{
  "status": "success",
  "data": {
    "success": true,
    "message": "App subscribed to webhooks successfully. You should now receive incoming messages."
  }
}

Business Profile

The business profile is fetched from and pushed to Meta live; it is not stored locally.

Get Business Profile

GET /api/accounts/{id}/business_profile

Response

{
  "status": "success",
  "data": {
    "messaging_product": "whatsapp",
    "address": "123 Main St",
    "description": "We sell great things",
    "vertical": "RETAIL",
    "email": "hello@example.com",
    "websites": ["https://example.com"],
    "profile_picture_url": "https://...",
    "about": "Open 9-5"
  }
}

Update Business Profile

PUT /api/accounts/{id}/business_profile

Request Body

{
  "messaging_product": "whatsapp",
  "address": "123 Main St",
  "description": "We sell great things",
  "vertical": "RETAIL",
  "email": "hello@example.com",
  "websites": ["https://example.com"],
  "about": "Open 9-5"
}

Returns the refreshed profile (or { "message": "Profile updated successfully" } if the re-fetch fails).

Update Profile Picture

Upload a new profile picture. Send the image as multipart/form-data with a file field.

POST /api/accounts/{id}/business_profile/photo

Response

{
  "status": "success",
  "data": {
    "message": "Profile picture updated successfully",
    "handle": "meta-upload-handle"
  }
}

Embedded Signup

KiteGreet supports Meta’s Embedded Signup flow, letting users connect a WhatsApp Business account without manually copying credentials. See the Embedded Signup feature guide for the end-to-end flow.

Get Embedded Signup Config

Public helper the frontend uses to bootstrap the Meta JS SDK with the org’s app credentials.

GET /api/embedded-signup/config

Response

{
  "status": "success",
  "data": {
    "whatsapp_app_id": "1234567890",
    "whatsapp_config_id": "9876543210",
    "whatsapp_api_version": "v21.0"
  }
}

Exchange Token

Exchange the temporary authorization code returned by the Embedded Signup dialog for a permanent access token, then create (or update) the account. Phone and WABA IDs are auto-discovered from the token if omitted, and the flow attempts auto-registration and webhook subscription.

POST /api/accounts/exchange-token

Request Body

{
  "code": "AQD...",
  "phone_id": "123456789",
  "waba_id": "987654321",
  "name": "Support Line",
  "webhook_verify_token": "your_custom_verify_token"
}

Only code is required — phone_id, waba_id, name, and webhook_verify_token are optional.

Response

{
  "status": "success",
  "data": {
    "account": {
      "id": "uuid",
      "name": "Support Line",
      "phone_id": "123456789",
      "business_id": "987654321",
      "status": "active",
      "has_access_token": true
    },
    "pin": "123456",
    "warning": "Registration failed: ...",
    "webhook_subscribed": true
  }
}

pin is present only when auto-registration succeeded; warning is present only when registration failed. webhook_subscribed is false when the account connected but Meta rejected the webhook subscription; retry it with the Subscribe action on the account. If phone_id or waba_id is omitted and the token can reach more than one, the request returns 400 and connects nothing. See the Embedded Signup guide for details.

Account Status

Status	Description
pending_registration	Account created via embedded signup, phone number not yet registered
active	Account is connected and working

Quality Rating

The Test Connection endpoint surfaces Meta’s live quality rating for the phone number:

Rating	Description
GREEN	High quality, no issues
YELLOW	Some issues, review messages
RED	Low quality, account at risk

Tip

Monitor your quality rating regularly. A RED rating can lead to messaging limits or account suspension.