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

Clerk.io Merchandising API

The Merchandising API from Clerk.io — 4 operation(s) for merchandising.

Clerk.io Merchandising API is one of 14 APIs that Clerk.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 16 operations across 4 paths. It is described by OpenAPI 3.2.0, at version 2.

Requests are made against a single base URL, https://api.clerk.io/v2.

16 operations 4 paths 0 schemas 4 DELETE4 GET4 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://api.clerk.io/v2
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Clerk.io Merchandising API declares 1 security scheme for authenticating requests. An API key is passed in the query as key (sec0). By default, every request must be authenticated.

Paths & Operations 16

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

Merchandising 16
GET
/customized_search
/customizedsearch
customized-searches-get 3 params → 200400
POST
/customized_search
/customizedsearch
customized-searches-post body → 200400
PATCH
/customized_search
/customizedsearch
customized-searches-patch body → 200400
DELETE
/customized_search
/customizedsearch
customized-searches-delete 3 params → 200400
GET
/merchandising
/merchandising
merchandising-get 3 params → 200400
POST
/merchandising
/merchandising
merchandising-post body → 200400
PATCH
/merchandising
/merchandising
merchandising-patch body → 200400
DELETE
/merchandising
/merchandising
merchandising-delete 3 params → 200400
GET
/redirects/
/redirects
redirects-get 3 params → 200400
POST
/redirects/
/redirects
redirects-post body → 200400
PATCH
/redirects/
/redirects
redirects-patch body → 200400
DELETE
/redirects/
/redirects
redirects-delete 3 params → 200400
GET
/synonyms
/synonyms
synonyms-get 3 params → 200400
POST
/synonyms
/synonyms
synonyms-post body → 200400
PATCH
/synonyms
/synonyms
synonyms-patch body → 200400
DELETE
/synonyms
/synonyms
synonyms-delete 3 params → 200400

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clerk-io-merchandising-api-openapi.yml Raw ↑

Other APIs Clerk.io publishes across the network.

Clerk.js Client Library
Clerk.io Accessories API
Clerk.io Audiences API
Clerk.io Campaigns API
Clerk.io Catalog API
Clerk.io Logging API
Clerk.io Parcels API
Clerk.io Privacy API
Clerk.io Product Data API
Clerk.io Recommendations API
Clerk.io Search API
Clerk.io Subscribers API
Where this information came from

This is an independent, third-party profile of Clerk.io Merchandising 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.