How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mapp Marketing Cloud Variant Data Operations API

Endpoints for variant data operations

Mapp Marketing Cloud Variant Data Operations API is one of 37 APIs that Mapp Marketing Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Variant Data Operations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an API reference, authentication docs, and a changelog.

This API exposes 8 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.1.

Requests are made against a single base URL, https://api.mapp.com.

8 operations 4 paths 10 schemas 3 DELETE2 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.1
Base URL
https://{engage-host}/api/rest/v19
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Mapp Marketing Cloud Variant Data Operations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Keycloak). By default, every request must be authenticated.

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 3 DELETE, 2 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Variant Data Operations 8

Endpoints for variant data operations

POST
/api/product-catalog/v1/catalogs/{catalogId}/variants
Add a new variant or add missing data to an existing variant.
addVariant 1 param body → 400202500
GET
/api/product-catalog/v1/catalogs/{catalogId}/variants
List variants with cursor pagination
getPaginatedVariants 8 params → 200400404204500
PUT
/api/product-catalog/v1/catalogs/{catalogId}/variants/{variantId}
Create or fully replace a variant
upsertVariant 2 params body → 500400202
DELETE
/api/product-catalog/v1/catalogs/{catalogId}/variants/{variantId}
Delete a variant by ID
deleteVariant 2 params → 202400404500
GET
/api/product-catalog/v1/catalogs/{catalogId}/variants/{variantId}
Get a single variant by ID
getVariant 4 params → 500404200204400
PATCH
/api/product-catalog/v1/catalogs/{catalogId}/variants/{variantId}
Partially update a variant
partialUpdateVariant 2 params body → 400202500
DELETE
/api/product-catalog/v1/catalogs/{catalogId}/variants/
Delete all variants in a catalog
deleteAllCatalogData 1 param → 500202400
DELETE
/api/product-catalog/v1/catalogs/{catalogId}/variants/{variantId}/attributes
Delete attributes from a variant
deleteVariantAttributes 2 params body → 404500202400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are VariantFlatViewResponse (39 properties), AddVariantOperationFlatSchema (34 properties), UpsertVariantOperationFlatSchema (33 properties), PartialUpdateVariantOperationFlatSchema (33 properties). Each schema is shown below with its type and property counts.

PartialUpdateVariantOperationFlatSchema
object
Flat request payload for partially updating a SOURCE variant, where: - predefined SOURCE attributes are documented as fields here. - custom SOURCE attributes a…
33 properties
UpsertVariantOperationFlatSchema
object
Flat request payload for creating or fully replacing a SOURCE variant, where: - predefined SOURCE attributes are documented as fields here. - custom SOURCE att…
33 properties
CatalogOperationResponseDTO
object
6 properties
AddVariantOperationFlatSchema
object
Flat request payload for adding a SOURCE variant, where: - predefined SOURCE attributes are documented as fields here. - custom SOURCE attributes are added dyn…
34 properties 1 required
PaginationCursorDTO
object
Only set when pagination is used
4 properties
ErrorResponse
object
4 properties
PaginatedVariantsResponseDTO
object
2 properties
VariantOperationResponseDTO
object
9 properties
SkippedAttributesDTO
object
3 properties
VariantFlatViewResponse
object
Flat variant payload based on the unified product catalog schema, where: - predefined SOURCE attributes are documented as fields here. - custom SOURCE attribut…
39 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mapp-variant-data-operations-api-openapi.yml Raw ↑

Other APIs Mapp Marketing Cloud publishes across the network.

Mapp Marketing Cloud Address Attributes API
Mapp Marketing Cloud Analysis API
Mapp Marketing Cloud Async API
Mapp Marketing Cloud Audit Log API
Mapp Marketing Cloud Authorization API
Mapp Marketing Cloud Automation API
Mapp Marketing Cloud Available Objects API
Mapp Marketing Cloud Blacklist API
Mapp Marketing Cloud Catalog Metadata Operations API
Mapp Marketing Cloud CMS API
Mapp Marketing Cloud Contact API
Mapp Marketing Cloud Content API
Where this information came from

This is an independent, third-party profile of Mapp Marketing Cloud Variant Data Operations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.