# Ciloo

> Ciloo is a Rotterdam-headquartered global platform for branded products and promotional merchandise.
> Enterprises run a Ciloo brand store, and orders placed in it are produced on demand by a local
> production partner near the recipient — cutting cost, waste and shipping distance while keeping brand
> control central. Ciloo exposes two documented APIs: a per-brand-store Cart API (OAuth 1.0a) for
> placing items in a customer's cart and handing them a signed auto-login link, and a Printer API
> integration (bidirectional webhooks) for routing orders to production partners and receiving
> production and shipping status back.

Generated 2026-08-12 by API Evangelist. Ciloo does not publish an llms.txt of its own
(https://ciloo.com/llms.txt and https://api.cilooprint.com/llms.txt both return 404), so this file is
generated from the provider's published documentation and the artifacts in this repository.

## APIs

- [Ciloo Cart API](https://api.cilooprint.com/ciloo-cart-api-documentation/): OAuth 1.0a (HMAC-SHA1)
  REST API on the `ciloo/v1` namespace of a brand store — get/add/update/remove cart items, mint
  per-customer OAuth credentials, and issue one-hour auto-login tokens. Customer records are created
  and updated through the WooCommerce `wc/v3` namespace on the same host. Documentation version 2.0.0,
  last updated 2025-08-18.
- [Ciloo Printer API Integration](https://api.cilooprint.com/printer-api-integration/): order submission
  from Ciloo to a production partner's own endpoint, and production-status plus shipping callbacks from
  the partner back to a Ciloo-owned inbound URL.

## Base URL

There is no single shared API host. Every brand store is its own hostname — a Ciloo-hosted
`<tenant>.cilooprint.com` subdomain or a customer-owned domain — and the API is served from `/wp-json`
on that host. The documentation writes the base as `https://your-domain.com/wp-json/ciloo/v1/`.

## Specs and machine-readable artifacts

- OpenAPI 3.1 (generated by API Evangelist from the provider's reference and Postman collection):
  openapi/ciloo-cart-api-openapi.yml
- Postman collection (first-party, published by Ciloo):
  collections/ciloo-cart-api.postman_collection.json
- Webhook/callback catalog: asyncapi/ciloo-printer-webhooks.yml
- Authentication profile: authentication/ciloo-authentication.yml
- API conventions: conventions/ciloo-conventions.yml
- Error catalog: errors/ciloo-problem-types.yml
- Data model: data-model/ciloo-data-model.yml
- Lifecycle: lifecycle/ciloo-lifecycle.yml
- Conformance: conformance/ciloo-conformance.yml
- Agent skills: skills/_index.yml

## Docs

- [API knowledge centre](https://api.cilooprint.com/)
- [Cart API reference](https://api.cilooprint.com/ciloo-cart-api-documentation/)
- [Printer API integration guide](https://api.cilooprint.com/printer-api-integration/)
- [Postman collection download](https://api.cilooprint.com/wp-content/uploads/2025/09/Ciloo-Cart-API-Generic-Implemetation.postman_collection.json_.zip)
- [Platform overview](https://ciloo.com/platform-overview/)
- [Integrations and partners](https://ciloo.com/integrations-partners/)
- [Support (Zendesk)](https://support.ciloo.com/hc/en-us) — support@ciloo.com

## What Ciloo does not publish

- No OpenAPI or AsyncAPI document of its own.
- No SDK on any public package registry, and no GitHub organization; the PHP, JavaScript and Python
  reference implementations are printed inline in the documentation.
- No pricing page, no public developer sign-up — access comes with a brand-store contract.
- No published rate limits and no rate-limit response headers.
- No idempotency contract on any write operation.
- No status page, SLA or deprecation policy.
- No /.well-known/ documents, no security.txt, no MCP server and no A2A agent card.