After sending your catalog data, you must trigger an Index API call to inform Bloomreach about the new catalog data and to index that catalog.

If you have multiple PATCH requests that need to be indexed for the same content catalog, you only need to call the Index API once to index all of them. If you want data to be uploaded in the order it was sent, then you should allow the PUT/PATCH jobs to finish before running the Index API.

🚧

Content from newly sent catalog data will not be searchable until you call the Index API. Likewise, changes to make an attribute searchable or not searchable will not be applied until you call the Index API. If you have recently sent content catalog data or configured your attributes but your content search isn’t working as expected, try running the Index API again.

Endpoints

• Production: https://api.connect.bloomreach.com/dataconnect/api/v1/
• Staging: https://api-staging.connect.bloomreach.com/dataconnect/api/v1/

Job ID

The response contains a job ID that can be used to query for status. After this job is successful, your catalog item data will be available to query in the Search API endpoints after Bloomreach caches have cleared.

🚧

Processing

Bloomreach processes the index requests sequentially, so there may be a delay before you can see the results. This depends on the amount of data and Index API requests you have queued.