How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ciloo Cart API

OAuth 1.0a (HMAC-SHA1) REST API on the ciloo/v1 namespace of a Ciloo brand store. Read, add, update and remove cart items; mint per-customer OAuth credentials from admin credentials; and issue one-hour auto-login tokens that drop a customer straight into the store's cart or order history. Customer records are created and updated through the WooCommerce wc/v3 namespace on the same host. Requests are form-encoded — the provider documents that a JSON content type breaks the signature.

Ciloo Cart API is one of 4 APIs that Ciloo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cart, Customers, Authentication, and Print on Demand. The published artifact set on APIs.io includes API documentation, an API reference, a getting-started guide, an OpenAPI specification, and authentication docs.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://{store_domain}.

4 operations 3 paths 4 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://{store_domain}/wp-json/ciloo/v1
Authentication
HTTP Oauth, HTTP Basic
Resource Areas
1

Authentication & Security 2

Ciloo Cart API declares 2 security schemes for authenticating requests. It uses HTTP oauth authentication (oauth1a). It accepts HTTP basic authentication (basicAuth).

  • oauth1a — OAuth 1.0a with the HMAC-SHA1 signature method (RFC 5849 "OAuth" HTTP authentication scheme). Required parameters: oauthconsumerkey, oauthsignaturemethod=HMAC-…
  • basicAuth — HTTP Basic authentication using the consumer key as username and consumer secret as password. Documented as used only by generateCustomerLoginToken.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Cart 4

Cart item read/write operations on the ciloo/v1 namespace.

GET
/wp-json/ciloo/v1/cart
Get cart items
getCartItems → 200401400
POST
/wp-json/ciloo/v1/cart/add-item
Add item to cart
addCartItem body → 200400401
PUT
/wp-json/ciloo/v1/cart/items/{asset_id}
Update cart item
updateCartItem 1 param body → 200400401
DELETE
/wp-json/ciloo/v1/cart/items/{asset_id}
Remove cart item
removeCartItem 1 param → 200400401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CartItem (8 properties), ErrorResponse (3 properties), CartResponse (3 properties), SuccessResponse (2 properties). Each schema is shown below with its type and property counts.

CartResponse
object
3 properties
SuccessResponse
object
2 properties
ErrorResponse
object
The documented Ciloo error envelope. Note this is a bespoke envelope, not RFC 9457 problem+json.
3 properties
CartItem
object
One item in a Ciloo brand-store cart, keyed in responses by its assetid.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ciloo-cart-api-openapi.yml Raw ↑

Other APIs Ciloo publishes across the network.

Ciloo Printer API Integration
Ciloo Authentication API
Ciloo Customers API
Where this information came from

This is an independent, third-party profile of Ciloo Cart API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.