Skip to main content
The Verzla Enrichment API is a REST surface for trusted third-party providers that enrich a merchant’s product catalog. You read products and the merchant’s attribute templates, generate proposals with your models, and submit them back as pending revisions for a human reviewer to accept or reject. Nothing you submit goes live automatically. Every proposal lands as a revision in the merchant’s review queue, so your integration can be bold while the merchant stays in control.

The Pipeline

Understand the read → enrich → submit → review loop before you write any code.

Quickstart

From API key to your first accepted proposal in a handful of requests.

Request an API Key

Every call is authenticated. Start here — you cannot read or submit without a key.

API Reference

Every endpoint, with request and response shapes and copy-paste examples.

​
What you can do

1

Fetch attribute templates

Read the merchant’s attribute templates first. They define the schema — which attributes matter, their units, data types, and priority — so your model enriches against the right shape instead of guessing.
2

Fetch products

Pull the catalog as a paginated list (with an optional modifiedSince filter for incremental syncs) or look up specific SKUs.
3

Submit proposals with confidence

Send enriched fields back as a submission. Attach a confidence score (0–100) to each item so reviewers can triage high-confidence work first.
4

Track your acceptance rate

Check how your proposals are performing over time and tune your models against real reviewer feedback.

​
Base URL

All endpoints are served under a single base URL and the /api/enrichment prefix. 
https://api.verzla.com/api/enrichment
Ask your Verzla contact for the exact base URL for your environment — staging and production differ. Every example in these docs uses the placeholder above.