Orders
Read your order history and record new sales - for example, to push point-of-sale or third-party orders into Cloove.
All endpoints share the prefix /v1/orders and authenticate with an API key.
List orders
GET /v1/ordersQuery parameters
{
"message": "Orders retrieved",
"data": [
{
"id": "o1a2b3c4-...",
"shortCode": "ORD-1234",
"status": "COMPLETED",
"totalAmount": 5000,
"amountPaid": 5000,
"remainingAmount": 0,
"paymentMethod": "CASH",
"customer": { "id": "ct1a2b3c-...", "name": "Ada Lovelace" },
"date": "2026-01-15T10:00:00.000Z"
}
],
"meta": { "total": 1, "page": 1, "perPage": 50, "totalPages": 1, "hasMore": false }
}Get an order
GET /v1/orders/:idReturns a single order with its line items. Responds 404 not_found if the ID doesn’t
belong to your business.
Record an order
POST /v1/ordersRecords a sale. Always send an Idempotency-Key header - recording is a money-affecting
write, and the key guarantees a retry won’t double-count the sale.
Body
Line item
{
"items": [
{ "product_id": "p1a2b3c4-...", "product_name": "Jollof Rice", "quantity": 2 }
],
"payment_method": "CASH",
"amount_paid": 5000,
"customer_id": "ct1a2b3c-...",
"channel": "api"
}Response 201 Created - the recorded order.
Recording an order emits an order.created webhook, so downstream systems
can react in real time.
Last updated on