Cajari API Documentation

Overview

The Cajari API provides access to accounts, merchant marketplaces, executions, and results so that you can integrate our data into your system.

The API is available in two versions:

V2 API (Recommended)

The V2 API introduces merchant marketplace-centric execution triggering, allowing you to target specific merchant marketplaces rather than triggering all marketplaces for a Seller Central account.

Key Features:

Target specific merchant marketplaces
Automatic Seller Central account selection
More precise control over executions

View V2 Documentation

V1 API (Legacy)

The V1 API triggers executions for all merchant marketplaces associated with a Seller Central account.

This is the original API behavior.

Key Features:

Trigger all marketplaces at once
Requires Seller Central account ID
Backwards compatible

View V1 Documentation

Quick Comparison

Endpoint	V2 (Recommended)	V1 (Legacy)
POST /executions Trigger Execution	Requires `merchant_marketplace_id` Runs single merchant marketplace `seller_central_account_id` optional (auto-selected)	Requires `seller_central_account_id` Runs all active merchant marketplaces for that account
GET /seller_central_accounts	Returns actual Seller Central account data with `last_used_at` and `last_login_status`	Returns merchant marketplace data with `skill_*` fields
GET /merchant_marketplaces	Cleaner response with `last_execution_started_at` and `last_execution_status` Only returns active merchant marketplaces	Includes `seller_central_account_*` fields, `status`, `merchant_token` Supports `include_disabled` parameter
GET /executions	Excludes `seller_central_account_name`	Includes `seller_central_account_name`
GET /results	Excludes `seller_central_account_name` Reordered: identifiers first, result data last	Includes `seller_central_account_name`
GET /reports	Identical
GET /whoami	Identical

Common to Both Versions

The following features work the same in both V1 and V2:

Authentication: Bearer token using your API key
Webhooks: Configured in Account Settings, sent when results are ready
Response Format: JSON with status, error, and data fields

See the individual version documentation for complete details.