---
title: "Working with catalog data"
slug: "product-catalog-api-working-with-catalog-data"
updated: 2026-05-29T13:31:43Z
published: 2026-05-29T13:31:43Z
canonical: "docs.mapp.com/product-catalog-api-working-with-catalog-data"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Working with catalog data

The Product Catalog API provides multiple ways to manage variant data. The behavior depends on the HTTP method used.

---

## Single and bulk operations

The API supports operations for individual variants as well as bulk processing.

| Operation type | Purpose |
| --- | --- |
| Single operations | Manage individual variants one at a time. |
| Bulk operations | Process multiple variants in a single request. |

---

## Behavior by HTTP method

| Method | Behavior |
| --- | --- |
| `GET` | Retrieves product or variant information. |
| `POST` | Adds new variant data or enriches existing variants with missing data. |
| `PUT` | Creates a variant or fully replaces existing variant data. |
| `PATCH` | Updates only the provided fields of an existing variant. |
| `DELETE` | Deletes variants or selected variant attributes. |

---

## Active status filtering

Some endpoints support filtering through the `activeStatusSearch` parameter.

The following values are supported:

- `ACTIVE_ONLY` - Returns only attributes where `isActive` is `true`.
- `INACTIVE_ONLY` - Returns only attributes where `isActive` is `false`.
- `ALL` - Returns all attributes regardless of the `isActive` value.

If the parameter is not provided, the behavior is equivalent to `ALL`.

> [!NOTE]
> Note
> 
> This filter applies to attribute status (isActive) and not to product or variant lifecycle status.

---

## Bulk processing behavior

- Bulk operations allow up to 1000 variant events in a single request.
- Bulk processing is not transactional.
- Each variant event is validated and processed independently.
- A failure in one variant event does not prevent other variant events from being processed successfully.
- Bulk operation responses contain separate lists for successful and failed events:
  - variant_events_success: Variant events that passed validation.
  - variant_events_failed: Variant events that failed validation.
- No official retry recommendation is currently defined.

### Bulk operation responses

Bulk operation responses contain separate lists for successful and failed events.

| Response field | Description |
| --- | --- |
| `variant_events_success` | Variant events that passed validation and processing. |
| `variant_events_failed` | Variant events that failed validation or processing. |

### Request limits

| Limit | Value |
| --- | --- |
| Maximum variants per request | 1000 |
| Maximum payload size | No explicit limit defined |

### Retry behavior

No official retry recommendation is currently defined.