API Reference

Complete reference of the ConformaESG REST API, generated from the official OpenAPI specification.

All ConformaESG endpoints are rooted under {{BASE_URL}}/api/v1/ and speak JSON over HTTPS. See Configuration for the base URL and API Conventions for shared patterns (identifiers, dates, errors, filtering).

Endpoint groups

GroupBase pathPurpose
Authentication/auth, /healthLogin, logout, CSRF, session introspection and health checks
API Keys/auth/api-keysPersonal access tokens and grantable scopes
Legacy Session & Entitlements/meLegacy user context endpoints for older integrations
Account Users/account/usersTenant users, roles and module permissions
Suppliers/suppliersCRUD for suppliers
Supplier Certifications/supplier-certificationsCompliance certificates attached to suppliers
Supplier Documents/suppliers/{supplierId}/...Supplier-owned document upload surfaces
Supplier Products/supplier/productsCatalog of items each supplier offers
Company Products/company/productsYour own product catalog
Company Profile/company/profileCompany profile and profile-owned documents
Documents/documentsGeneric document metadata, upload, download and presigned flow
Product Materials/product/materialsRaw materials, purchases, activities and documents
Chemicals/chemicalsChemical products with ZDHC levels
Purchases/purchasesSupplier purchase orders with status lifecycle
Purchase Documents/purchases/{purchaseId}/documentsPurchase-owned document uploads
Textile — Fabrics/textile/fabricsFabric product catalog
Textile — Yarns/textile/yarnsYarn product catalog
Textile — Fibers/textile/fibersFiber product catalog
Product Traceability/product/traceabilityEnd-to-end product journeys with processing stages
Traceability Records/traceabilityBatch-level traceability records
External Supplier Wizard/external-supplier-wizardFinal supplier wizard submission

Common behavior

  • List endpoints use the response shape documented per resource: plain arrays, items envelopes or data/meta/facets envelopes.
  • Path identifiers are always UUIDs.
  • All fields use camelCase.
  • Errors follow the standard error envelope.

HTTP verbs at a glance

VerbMeaning
GET /resourceList resources (may accept query filters)
GET /resource/{id}Fetch a single resource
POST /resourceCreate a resource
PATCH /resource/{id}Partially update a resource
DELETE /resource/{id}Delete a resource
Note

The canonical definition of the API is the OpenAPI spec (openapi.json). This reference is a human-friendly restatement of the same contract — whenever the two differ, the spec wins.