Skip to main content
Core Commerce APIs

Build on the same catalog the platform runs on.

REST APIs at https://api.catazenta.com — organized by commerce capability, not internal service names. The UI, syndication workers, specialist agents, and MCP all use this surface.

JSON bodies, JWT authentication, tenant-scoped catalog operations, and OpenAPI specs for every area — copy patterns into Postman or your integration today.

8OpenAPI API areas
/v1Versioned REST paths
1Catalog with MCP + ACC

How the APIs fit together​

Every integration reads and writes the same governed catalog — not a shadow API layer.

ConventionDetail
Base URLhttps://api.catazenta.com
FormatJSON request and response bodies
AuthAuthorization: Bearer <access_token> — see Authentication
TenantScope from JWT claims or X-Tenant-Id where applicable
ListsPaginated (page, page_size) — Pagination & errors
ContractsOpenAPI + Redoc on this site — OpenAPI & Postman
Same catalog as Agentic PIM

Specialist agents propose writes through the approval queue; MCP tools call the same REST paths. Your integrations participate in the same audit trail and channel rules.


Products​

Create and govern the catalog your AI and channels consume.

TaskStart here
Create / update productsProduct API · Recipe: create product
Variants & attributesProduct API · Update attributes
Categories & taxonomyCategory API · Attribute API
Completeness & gapsProduct intelligence · Completeness recipe
Search & dashboardSearch API

Product API

Products, variants, families, attribute values, completeness.

Category API

Category trees, nodes, product assignments.

Attribute API

Attribute definitions, groups, options, UoM.


Assets​

TaskStart here
Upload & manage mediaDAM API
Link assets to SKUsRecipe: link DAM
Renditions & foldersDAM guide

Workflows​

TaskStart here
Approvals & tasksWorkflows guide
Users, roles, permissionsIAM API
Service accountsService account recipe

Human gates in PIM workflows complement Agent Control Center approvals for agent-proposed writes.


Syndication​

TaskStart here
Connections & export profilesIntegration API
Export / import jobsJob API
Poll async job statusPoll export job
AmazonAmazon syndication · Connector
ShopifyShopify syndication

MCP equivalent: list_connections, quick_publish, create_export_job — see MCP tools.


API reference index​

Interactive Redoc pages generated from OpenAPI — one reference per backend area.

APIDescription
ProductProducts, models, families, completeness
CategoryCategory trees and assignments
AttributeAttribute definitions and options
DAMAssets, folders, renditions
IAMAuth, users, roles, tenants
IntegrationConnectors, connections, export/import
JobAsync import/export jobs and schedules
SearchDashboard and search endpoints

Download raw OpenAPI JSON → OpenAPI & Postman · Postman collection


Recipes — task-focused guides​

Copy-paste examples against https://api.catazenta.com — faster than browsing every endpoint.

All recipes → Recipes index


REST vs MCP vs in-product agents​

REST APIsMCPSpecialist agents (ACC)
Best forERP, custom pipelines, headlessClaude, ChatGPT, CursorScheduled runs, approvals, insights
AuthJWT / service accountOAuth or connector tokenPIM session (ai_mgmt)
WritesDirect API calls (RBAC)Named tool callsApproval queue → apply

→ MCP overview · Agentic PIM · API overview


Developer essentials​

TopicDoc
AuthenticationAuthentication
Pagination & errorsPagination & errors
VersioningAPI versioning
WebhooksWebhooks
OpenAPI downloadsOpenAPI & Postman
ChangelogChangelog
ArchitectureAPI-first platform

Get started​

  1. Complete Your first API call — login, list products, verify identity.
  2. Read Authentication — user JWT vs service accounts.
  3. Pick a capability above (products, DAM, syndication, …).
  4. Use Recipes for copy-paste task flows.
  5. Wire MCP when conversational or IDE automation fits better than raw REST.

Need access? Contact CataZenta for tenant credentials.