#Catalogs for Apps Beta


This guide introduces the catalog feature and explains why using catalogs to retrieve Akeneo data.
You will save time during development with catalogs because Akeneo PXM Studio manages your product selection and gives you direct access to the relevant data.

#What's a catalog?

A catalog is a selection of products defined by one or several criteria (families, categories, etc.)

Catalogs are only created by apps and configured by Akeneo users from Akeneo PXM Studio. This feature is only visible if the app manages catalogs.

Catalogs for apps

#Why use catalogs to retrieve product data?

Using Catalogs helps you better manage the product information you get from the Akeneo PXM Studio.

Most of the time, developers must design, develop and maintain a filter interface to allow users to configure their product selection: which products must be taken into account and which don't. Using catalogs for apps prevents you from adding this filtering interface to your app. When you retrieve product information related to a catalog, you only retrieve the data your app needs to process.

Moreover, with catalogs, you don't have to master the entire PIM structure anymore to deliver a relevant filtering interface, as the Akeneo PXM Studio already provides it to your users. Product Selection


To ensure Akeneo PXM Studio remains stable, we added some limits to catalogs:

  • Each app can create up to 15 catalogs.
  • A product selection can have up to 25 selection criteria.


#Automatic deactivation on catalogs

When a product selection becomes invalid, e.g. a selected category no longer exists, the PIM automatically disables the catalog.

In that case, your app receives an HTTP 200 response containing the following payload.

      "error": "No products to synchronize. The catalog \"65f5a521-e65c-4d7b-8be8-1f267fa2729c\" has been disabled on the PIM side. Note that you can get catalogs status with the GET /api/rest/v1/catalogs endpoint."

#Next steps

#Getting started with catalogs

To create and use a catalog, your app has to send some requests to the Akeneo REST API. This guide describes how to use the catalog features with your app.

#What you'll learn

After completing this tutorial, you'll be able to create and use catalogs to retrieve product data.


#Step 1: Ask for catalog scopes

To manage catalogs, you need to ask for at least 4 scopes:

  • read_products
  • read_catalogs
  • write_catalogs
  • delete_catalogs

In the documentation Ask for authorizations, you can discover how to ask for scopes.

Once Akeneo users accept these scopes during the app connection, you will be able to manage and use catalogs.

#Step 2: Create catalogs

Once your app is connected and gets the proper authorization, your app can start using catalogs.

To do so, your app has to create a catalog using the Create a new catalog endpoint. When your app creates a catalog, the API returns its UUID. You will use this catalog UUID to get information about the catalog and retrieve related products.

To help your users know how to configure a catalog, give it the most descriptive name possible.

By default, new catalogs are disabled. It means that until a user hasn't enabled it, you won't be able to retrieve products for this catalog.

Please note that only users can enable a catalog. Catalog settings

To help your users, you can redirect them directly to the catalog configuration interface on their Akeneo PXM Studio using the following URL structure:{catalog_uuid}

At any moment, you can verify if a catalog is enabled by calling the get catalog endpoint.

#Step 3: Get products using catalogs

The endpoint for retrieving the list of product UUIDs will be available soon!

Once you have an enabled catalog, you can paginate the corresponding product UUIDs using this endpoint.

#Next steps