Skip to main content
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

MethodPathScopePurpose
GET/attribute-templatescatalog:readFetch the merchant’s attribute schema
GET/productscatalog:readPaginated product export
GET/products/skuscatalog:readLook up products by SKU
POST/products/submissionscatalog:submitSubmit enrichment proposals
GET/acceptance-ratecatalog:readYour 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.