Clerk.io

Clerk.io API

The Clerk.io API provides REST endpoints for managing products, categories, orders, customers, recommendations, and search. The API uses a dual-key authentication model: a public key identifies the store and is used in browser-side requests, while a private key is required for sensitive operations and data ingestion. JSON is the primary payload format and SSL is required when sending the private key.

GitHub

Documentation

📖
Documentation
https://docs.clerk.io/
📖
GettingStarted
https://docs.clerk.io/docs/how-the-clerkio-platform-works
📖
Authentication
https://docs.clerk.io/docs/authentication

Other Resources

🔗
Errors
https://docs.clerk.io/docs/errors
🔗
Pagination
https://docs.clerk.io/docs/pagenation

API entry from apis.yml

apis.yml Raw ↑ 
aid: clerk-io:clerk-io-api
name: Clerk.io API
tags:
- Commerce
- Personalization
- Recommendations
- Search
humanURL: https://docs.clerk.io/
properties:
- url: https://docs.clerk.io/
  type: Documentation
- url: https://docs.clerk.io/docs/how-the-clerkio-platform-works
  type: GettingStarted
- url: https://docs.clerk.io/docs/authentication
  type: Authentication
- url: https://docs.clerk.io/docs/errors
  type: Errors
- url: https://docs.clerk.io/docs/pagenation
  type: Pagination
description: 'The Clerk.io API provides REST endpoints for managing products, categories, orders, customers,
  recommendations, and search. The API uses a dual-key authentication model: a public key identifies the
  store and is used in browser-side requests, while a private key is required for sensitive operations
  and data ingestion. JSON is the primary payload format and SSL is required when sending the private
  key.'