Clerk.io Accessories API
The Accessories API from Clerk.io — 1 operation(s) for accessories.
Work with this as data
Every API 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 apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/clerk-io-accessories-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Clerk.io Accessories API
version: '2'
description: 'Clerk.io e-commerce personalisation REST API. Ingest and manage catalog data (products, categories, pages, orders, order parcels, customers, accessories), run behaviour-ranked search and predictive search-as-you-type, request recommendation logics (popular, trending, new, complementary, substituting, visitor- and customer-personalised, category- and page-scoped), manage merchandising (custom search configurations, synonyms, redirects), drive audiences/campaigns/subscribers for email, log visitor behaviour events, and service GDPR privacy requests.
All endpoints live under https://api.clerk.io/v2. Authentication uses a dual-key model: the public `key` identifies the store and is safe in browser-side calls; `private_key` is additionally required for write and sensitive operations and MUST only be sent over SSL.'
contact:
name: Clerk.io Documentation
url: https://docs.clerk.io/
x-provenance:
method: searched
harvested: '2026-08-13'
source: https://docs.clerk.io/reference/ (ReadMe API Designer OpenAPI 3.1.0 fragments per reference page)
original: openapi/_original/clerk-io-api-settings-openapi-original.yml
note: Provider-published operation content is verbatim. API Evangelist added the document title/description, tags[] declarations and per-operation tag assignment; see overlays/clerk-io-api-overlay.yaml.
servers:
- url: https://api.clerk.io/v2
security:
- sec0: []
tags:
- name: Accessories
paths:
/accessories:
get:
summary: /accessories
description: ''
operationId: accessories-get
parameters:
- name: key
in: query
description: Your stores public API key.
required: true
schema:
type: string
- name: private_key
in: query
description: Your stores private API key.
required: true
schema:
type: string
- name: accessories
in: query
description: List of product ID's to get the data for.
schema:
type: array
items:
type: string
responses:
'200':
description: '200'
content:
application/json:
examples:
Result:
value: "{'status': 'ok',\n 'accessories':[\n \t{'product': 'AV-DHONO',\n \t 'accessories': ['JBL-GO'],\n \t 'directed_accessories': ['LDY84']}\n ]\n }"
'400':
description: '400'
content:
application/json:
examples:
Result:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Accessories
post:
summary: /accessories
description: ''
operationId: accessories-post
requestBody:
content:
application/json:
schema:
type: object
required:
- key
- private_key
properties:
key:
type: string
description: Your stores public API key.
private_key:
type: string
description: Your stores private API key.
accessories:
type: array
description: list of accessory objects
responses:
'200':
description: '200'
content:
application/json:
examples:
Result:
value: '{''status'': ''ok''}'
'400':
description: '400'
content:
application/json:
examples:
Result:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Accessories
patch:
summary: /accessories
description: ''
operationId: accessories-patch
requestBody:
content:
application/json:
schema:
type: object
required:
- key
- private_key
properties:
key:
type: string
description: Your stores public API key.
private_key:
type: string
description: Your stores private API key.
accessories:
type: array
description: list of accessory objects
responses:
'200':
description: '200'
content:
application/json:
examples:
Result:
value: '{''status'': ''ok''}'
'400':
description: '400'
content:
application/json:
examples:
Result:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Accessories
delete:
summary: /accessories
description: ''
operationId: accessories-delete
parameters:
- name: key
in: query
description: Your stores public API key.
required: true
schema:
type: string
- name: private_key
in: query
description: Your stores private API key.
required: true
schema:
type: string
- name: accessories
in: query
description: List of product ID's to delete accessories for
schema:
type: array
items:
type: string
responses:
'200':
description: '200'
content:
application/json:
examples:
Result:
value: '{''status'': ''ok'' }'
'400':
description: '400'
content:
application/json:
examples:
Result:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Accessories
components:
securitySchemes:
sec0:
type: apiKey
name: key
in: query
x-default: your_api_key