API Reference - Verzla Enrichment

All endpoints are served under the /api/enrichment prefix of your environment’s base URL and are authenticated with the X-Api-Client-Key header. See Making authenticated requests for the auth model.

https://api.verzla.com/api/enrichment

Endpoints

Method	Path	Scope	Purpose
`GET`	`/attribute-templates`	`catalog:read`	Fetch the merchant’s attribute schema
`GET`	`/products`	`catalog:read`	Paginated product export
`GET`	`/products/skus`	`catalog:read`	Look up products by SKU
`POST`	`/products/submissions`	`catalog:submit`	Submit enrichment proposals
`GET`	`/acceptance-rate`	`catalog:read`	Your acceptance metrics

Conventions

Content type — request and response bodies are JSON (application/json).
Organization scoping — the merchant organization is resolved from your API key; you never pass an org identifier.
Errors — failures use standard HTTP status codes with a message body: 400 (bad request), 401 (unauthenticated), 403 (missing scope).
Pagination — offset-based via page / pageSize, with totalElements and totalPages in the response.