Ciloo

Ciloo is a Rotterdam-headquartered global platform for branded products and promotional merchandise. Enterprises run a branded Ciloo store — business cards, apparel, stationery, signage, corporate gifts and sales collateral — and every order placed in it is produced on demand by a vetted production partner near the recipient, which Ciloo positions as cutting cost, waste and shipping distance while keeping brand control central. The platform is used by manufacturing, medical-device, professional- services and franchise organisations, and integrates with digital asset management (Frontify, Bynder, Canto, Aprimo, Papirfly, Brandfolder, Marvia), procurement and ERP (SAP Ariba, S/4HANA, Proactis, Proqura, Exact), SSO, and WooCommerce. Ciloo documents two APIs on its own knowledge centre at api.cilooprint.com: a per-brand-store Cart API secured with OAuth 1.0a, and a bidirectional Printer API integration that pushes orders to production partners and receives production and shipping status callbacks in return.

Ciloo publishes 4 APIs on the APIs.io network, including Cart API, Authentication API, Customers API, and 1 more. Tagged areas include Company, Printing, Branded Merchandise, Promotional Products, and Print on Demand.

The Ciloo catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Ciloo’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, and 20 more developer resources.

🌐 Visit website 📡 Source on GitHub

30.1/100 thin ▬ flat Agent 29/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

4 APIs

Company Printing Branded Merchandise Promotional Products Print on Demand E-Commerce Digital Asset Management Procurement Fulfillment Marketing

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 30.1/100 · thin

Contract Quality 4.1 / 19

Developer Ergonomics 8.3 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.8 / 10

Contract Governance 0.4 / 9

Discoverability 5.4 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/ciloo: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

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 credent...

Ciloo Printer API Integration

Bidirectional order integration between Ciloo and its production partners. Ciloo POSTs a print order — items, print components with artwork paths and substrate attributes, and s...

Ciloo Authentication API

OAuth key provisioning and auto-login token issuance.

Ciloo Customers API

Customer lifecycle via the WooCommerce REST API v3 namespace, as documented by Ciloo.

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Ciloo Cart API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Ciloo Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Ciloo Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Ciloo Printer Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Ciloo Authentication

http · 2 schemes

SECURITY

Ciloo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

Postman

Postman

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

Contact

Contact

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 1

Properties that don't map to a standard resource type

CaseStudies

CaseStudies

Source (apis.yml)

aid: ciloo
name: Ciloo
description: 'Ciloo is a Rotterdam-headquartered global platform for branded products and promotional merchandise. Enterprises
  run a branded Ciloo store — business cards, apparel, stationery, signage, corporate gifts and sales collateral — and every
  order placed in it is produced on demand by a vetted production partner near the recipient, which Ciloo positions as cutting
  cost, waste and shipping distance while keeping brand control central. The platform is used by manufacturing, medical-device,
  professional- services and franchise organisations, and integrates with digital asset management (Frontify, Bynder, Canto,
  Aprimo, Papirfly, Brandfolder, Marvia), procurement and ERP (SAP Ariba, S/4HANA, Proactis, Proqura, Exact), SSO, and WooCommerce.
  Ciloo documents two APIs on its own knowledge centre at api.cilooprint.com: a per-brand-store Cart API secured with OAuth
  1.0a, and a bidirectional Printer API integration that pushes orders to production partners and receives production and
  shipping status callbacks in return.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://ciloo.com/wp-content/uploads/2022/01/Ciloo-Logo-2021.png
url: https://raw.githubusercontent.com/api-evangelist/ciloo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:marketing-integration-graph
specificationVersion: '0.23'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Printing
- Branded Merchandise
- Promotional Products
- Print on Demand
- E-Commerce
- Digital Asset Management
- Procurement
- Fulfillment
- Marketing
tags_raw:
- Company
- Printing
- Branded Merchandise
- Promotional Products
- Print On Demand
- eCommerce
- Digital Asset Management
- Procurement
- Fulfillment
- Marketing
apis:
- aid: ciloo:ciloo-cart-api
  name: Ciloo Cart API
  description: 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.
  humanURL: https://api.cilooprint.com/ciloo-cart-api-documentation/
  baseURL: https://{store_domain}/wp-json/ciloo/v1
  tags:
  - Cart
  - Customers
  - Authentication
  - Print on Demand
  tags_raw:
  - Cart
  - Customers
  - Authentication
  - Print On Demand
  properties:
  - type: Documentation
    url: https://api.cilooprint.com/ciloo-cart-api-documentation/
  - type: APIReference
    url: https://api.cilooprint.com/ciloo-cart-api-documentation/#api-endpoints-reference
  - type: GettingStarted
    url: https://api.cilooprint.com/ciloo-cart-api-documentation/#authentication-setup
  - type: OpenAPI
    url: openapi/ciloo-cart-api-openapi.yml
  - type: Overlay
    url: overlays/ciloo-cart-api-overlay.yaml
  - type: Postman
    url: collections/ciloo-cart-api.postman_collection.json
  - type: Authentication
    url: authentication/ciloo-authentication.yml
  - type: ErrorCatalog
    url: errors/ciloo-problem-types.yml
  - type: DataModel
    url: data-model/ciloo-data-model.yml
- aid: ciloo:ciloo-printer-api
  name: Ciloo Printer API Integration
  description: Bidirectional order integration between Ciloo and its production partners. Ciloo POSTs a print order — items,
    print components with artwork paths and substrate attributes, and shipments with carrier and destination — to the partner's
    own order endpoint; the partner POSTs production-status and shipping callbacks, with tracking, back to a Ciloo-owned inbound
    callback URL. Authentication is agreed per partner rather than published.
  humanURL: https://api.cilooprint.com/printer-api-integration/
  baseURL: https://dashboard.cilooprint.com/ciloo-order-callback/printer-inbound
  tags:
  - Order
  - Webhook
  - Fulfillment
  - Printing
  tags_raw:
  - Orders
  - Webhooks
  - Fulfillment
  - Printing
  properties:
  - type: Documentation
    url: https://api.cilooprint.com/printer-api-integration/
  - type: Webhooks
    url: asyncapi/ciloo-printer-webhooks.yml
- aid: ciloo:ciloo-authentication-api
  name: Ciloo Authentication API
  description: OAuth key provisioning and auto-login token issuance.
  humanURL: https://api.cilooprint.com/ciloo-cart-api-documentation/
  baseURL: https://{store_domain}/wp-json/ciloo/v1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/ciloo-authentication-api-openapi.yml
- aid: ciloo:ciloo-customers-api
  name: Ciloo Customers API
  description: Customer lifecycle via the WooCommerce REST API v3 namespace, as documented by Ciloo.
  humanURL: https://api.cilooprint.com/ciloo-cart-api-documentation/
  baseURL: https://{store_domain}/wp-json/ciloo/v1
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/ciloo-customers-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://ciloo.com/
- type: DeveloperPortal
  url: https://api.cilooprint.com/
- type: Documentation
  url: https://api.cilooprint.com/
- type: APIReference
  url: https://api.cilooprint.com/ciloo-cart-api-documentation/#api-endpoints-reference
- type: GettingStarted
  url: https://api.cilooprint.com/ciloo-cart-api-documentation/#authentication-setup
- type: Support
  url: https://support.ciloo.com/hc/en-us
- type: Blog
  url: https://ciloo.com/blog/
- type: BlogRSS
  url: https://ciloo.com/feed/
- type: TermsOfService
  url: https://ciloo.com/terms-conditions/
- type: PrivacyPolicy
  url: https://ciloo.com/privacy-policy/
- type: Contact
  url: https://ciloo.com/contact/
- type: Integrations
  url: https://ciloo.com/integrations-partners/
- type: CaseStudies
  url: https://ciloo.com/case-studies/
- type: Postman
  url: collections/ciloo-cart-api.postman_collection.json
- type: Authentication
  url: authentication/ciloo-authentication.yml
- type: Conventions
  url: conventions/ciloo-conventions.yml
- type: ErrorCatalog
  url: errors/ciloo-problem-types.yml
- type: Lifecycle
  url: lifecycle/ciloo-lifecycle.yml
- type: Conformance
  url: conformance/ciloo-conformance.yml
- type: DataModel
  url: data-model/ciloo-data-model.yml
- type: Webhooks
  url: asyncapi/ciloo-printer-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/ciloo-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/ciloo-llms.txt
- type: Plans
  url: plans/ciloo-plans-pricing.yml
- type: RateLimits
  url: rate-limits/ciloo-rate-limits.yml
- type: DomainSecurity
  url: security/ciloo-domain-security.yml
x-vouched-by:
- Brandfolder
- Frontify
x-vouch-count: 2
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 20
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/ciloo"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/ciloo/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/ciloo/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.