API reference
Complete reference for the Export Template Management (ETM) API — every endpoint, request, and response, grouped by API version.
Browse Export Template Management endpoints, grouped by API version.
V2 is the modern, template-based surface — use it where it covers what you need (export templates, analyzer tests, async operations).
V1 covers the broader feature set — use it for everything V2 doesn't cover yet (metadata, revisions, tags, attribute aliases, export fields, marketing, custom form fields).
Both surfaces are actively supported. Pick the one that has the operations you need.
Every operation page below renders live request and response schemas from the upstream OpenAPI spec. Download the ETM OpenAPI specification (JSON) to import into Postman, generate clients, or feed into any OpenAPI-aware tool. Authentication uses ProductsUp Keycloak JWT — see Get access.
V2
Export templates
Create, list, and manage V2 export templates.
Analyzer tests
Template-based analyzer test management. Assign reusable validators from a curated catalog.
Operations
V2 batch and resource-level operations.
V1
Export templates and metadata
Export templates
V1 export template lifecycle — create, list, show, update, commit changes.
Revisions
Read prior revisions of an export template.
Tags
Tag and categorize export templates.
Metadata
Per-template metadata fields.
Attributes
Attributes
Add, configure, and remove attributes on an export template.
Attribute aliases
Map external attribute names to template attributes.
Attribute tags
Tag attributes for grouping and filtering.
Export fields
Field-level operations on an export template.
Marketing and custom forms
How is this guide?
Analyzer tests
Template-based validation system for export attributes — assign reusable, parameterised validators from a curated catalog.
Create export template with dependencies POST
Creates a complete export template including attributes and analyzer tests in one call. The operation is executed asynchronously (inline in Phase 1). Progress and results are available via GET /V2/operations/{operationId}. Returns 202 Accepted with Content-Location header pointing to the operation.