Introduction

The Cloove API lets you build on top of the same platform that powers Cloove’s dashboard - voice AI, WhatsApp messaging, catalog and order management, wallets and payouts, hosted storefronts, and checkout. Everything is a standard HTTPS REST API that returns JSON, authenticated with a single API key.

What you can build

API	Use it to
Vox	Place AI-powered outbound calls, list call history, and read numbers and agents.
Messaging	Read WhatsApp conversations and send text or template messages.
Contacts	Create and manage the customers behind orders and conversations.
Products	List, create, and update catalog products.
Orders	List orders and record new sales.
Wallet & payouts	Read balances, manage payout accounts, and initiate withdrawals.
Storefront	Power public browsing and ordering on hosted stores.
Checkout	Create payment links and run the checkout flow.
Webhooks	Receive real-time events when things happen on the platform.

Base URL

All requests go to a single HTTPS base URL:


https://api.clooveai.com

There is no separate hostname for test and live. The environment is selected by the API key you use - see Environments below.

Requests must be made over HTTPS. Plain HTTP requests are rejected.

How requests work

Authentication is via a bearer API key in the Authorization header. See Authentication.
Request bodies are JSON. Send Content-Type: application/json on every POST/PATCH.
Responses are JSON with a consistent shape - a human-readable message, a data payload, and meta on paginated lists. See API conventions.
Writes can be made idempotent with an Idempotency-Key header, so a retried request is never processed twice.

A successful response looks like this:


{
  "message": "Vox calls retrieved",
  "data": [ /* ... */ ],
  "meta": { "total": 42, "page": 1, "perPage": 20, "totalPages": 3, "hasMore": true }
}

Environments

Cloove has two isolated environments. The one you act in is chosen by your API key’s prefix - there is no environment header and no separate URL.

	Test	Live
Key prefix	`clv_test_…`	`clv_live_…`
Side effects (real calls, messages, money movement)	No	Yes
Data	Sandbox	Production
Rate limits	Same	Same

Develop and test against a test key, then switch to a live key for production. Webhook endpoints and signing secrets are also scoped per environment.

Next steps

Make your first authenticated call.

Quickstart

Keys, scopes, and access controls.

Authentication

Errors, rate limits, pagination, idempotency.

API conventions