Please ignore the Accept header(
Accept: application/json
) in the request examples. This is just a quirk of the example module.
After formatting your data, you must deliver it to Bloomreach using one of two methods:
- Direct API payload: send your catalog data directly via an API payload
- SFTP file : send your catalog data via a file on SFTP
There are two modes available to update your catalog data:
- PUT (full): replace the catalog’s data entirely
- PATCH (delta): make partial updates to the catalog's data
PUT mode
When you PUT records into a catalog, you replace the catalog’s data entirely. In PUT mode, the only operation allowed is ADD so that data loading can be parallelized and optimized for ingestion speed. We recommend sending your data through a SFTP file when using PUT mode.
You don't need to update the full catalog daily using PUT, and we recommend using PATCH mode if you need to make frequent updates (more than once per day). We recommend using PUT mode if you are updating a large part of your catalog data, but you should limit using PUT to once per day. In PUT mode, a configurable percentage of malformed records is allowed.
Before you begin
Before sending your content catalog data to Bloomreach via the Catalog Data Management API, ensure that you have the following:
- Formatted catalog data - Create your content catalog data according to the Format your Data page.
- Transfer Key - You need an API key for authentication that is unique to your merchant account. If you do not already have it, speak to your Bloomreach representative.
- Catalog names - Catalog names used in the Catalog Data Management API endpoints. Use the same value as your domain key in your search API requests.
- Authentication key - Required header for Catalog Data Management API requests. You should have received this during kickoff.
Endpoints
- Production:
https://api.connect.bloomreach.com/dataconnect/api/v1/
- Staging:
https://api-staging.connect.bloomreach.com/dataconnect/api/v1/
Authentication key
An API key will be provided for each environment in your account. This access key must accompany all API requests as a request header. Example value: merchantname-1066facc-94fb-450e-9f9c-b66d0b155fd2
Steps
For full updates
- If sending data through SFTP, upload your catalog data to your Bloomreach SFTP location.
- Send the Catalog Data Management PUT API request.
- Run the index API.
For delta updates
- If sending data through SFTP, upload your catalog data to your Bloomreach SFTP location.
- Send the Catalog Data Management PATCH API request.
- If order of data is important, wait for PATCH job to finish.
- Run the index API.
No malformed items allowed in catalog data
if there are any malformed items in your catalog data, the whole operation will be invalid and no changes will be applied.
Send Data as API payload
To send your catalog data directly via an API payload, you must convert all of the operations into a single JSON Patch, which is an array of catalog records. In your Catalog Data Management API request body, include the catalog records.
The max size of a single API payload is 5MB.
[{
"op":"add",
"path":"/items/awesome_omelette_pdf",
"value":{
"attributes":{
"title":"Awesome Omelette",
"url":"https://www.homeoasis.com/pdf/awesome-omelette.pdf",
"medium_image_url":"https://www.homeoasis.com/images/recipe/201851/img1.jpg",
"rating":4.7,
"category":[
"PDF",
"Breakfast"
],
},
"@import":{
"path":"/pdfs/awesome_omelette.pdf"
}
}
},
{
"op":"add",
"path":"/items/awesome_omelette_video",
"value":{
"attributes":{
"title":"How to Make Our Awesome Omelette",
"url":"https://www.homeoasis.com/video/awesome-omelette-video.html",
"description":"Follow along our Awesome Omelette recipe with this companion video.",
"medium_image_url":"https://www.homeoasis.com/images/recipe/201851/img1.jpg",
"rating":4.7,
"video_id":HDRS2748,
"video_duration":5,
"category":[
"Videos",
"Breakfast"
],
},
}
}]
Mandatory field for suggestions
url
field is mandatory for product and attribute suggestions to be returned in the Autosuggest API.
Send Data as a file through SFTP
To send your catalog data via a file on SFTP, you must convert all of the patch operations into a file of JSONLines. Each line should only contain one patch operation. In your Catalog Data Management API request body, include the relative path to the file location.
Feed files may be sent uncompressed, or be compressed using gzip. The max size of a single API payload is 5MB.
In the request body, provide the paths to your catalog files as relative paths. For example, if your catalog files are in a folder named "content_en", then the request body should look like the following:
[
"{catalog name}/{catalog1.jsonl}",
"{catalog name}/{catalog2.jsonl}
]
{"op": "add", "path": "/items/item-123", "value": {...}} //First item record
{"op": "add", "path": "/items/item-456", "value": {...}} //Second item record
{"op": "add", "path": "/items/item-789", "value": {...}} //Third item record, etc.
…
When to use SFTP transfer
Other than the case that you have already been using SFTP File Transfer in your organization's workflow and that it's convenient for you, there are other reasons why you can consider using it:
- If you want to send more than 1 GB data, which is not possible through a direct payload.
- If you're sending sensitive data, SFTP is a highly secure option.
- SFTP transfer lets you independently control when you want to send the data and when to ingest it (or even send it to an intermediary server).
SFTP Endpoints
- Production: sftp.connect.bloomreach.com (3.82.164.133, port 22)
- Staging: sftp-staging.connect.bloomreach.com (54.211.108.247, port 22)
Your sftp command should look like the following:
sftp -i ~/path/to/private_key @sftp-staging.connect.bloomreach.com
Provide Bloomreach with public keys that will need access to each environment. More than one can be provided for each environment, and we advise using different public keys for staging and production.
SFTP tips
SFTP directory structureAny catalog data files should be sent via the SFTP location provided in the SFTP Endpoints section. We suggest organizing catalogs into their own folders to help with debugging. For example, you could create a folder called <catalog_name> and then place files related to that catalog in this folder.
File namingWe suggest naming your catalog data files to include the catalog name, the type of modification (put/full, patch/delta) and a datetime version identifier. This will help with debugging. For example, if your catalog is named <catalog_name>, you could name your file 20200410-090909-<catalog_name>_full.jsonl
Storage lengthFiles sent to the Bloomreach SFTP are stored for 30 days. Files that are older than 30 days will be automatically deleted and cleared.
Job ID
The response contains a job ID that can be used to query for status.
Sample PUT request
PUT | https://api.connect.bloomreach.com/dataconnect/api/v1/accounts/{account_id}/catalogs/{catalog_name}/items |
Headers | |
Authorization | Bearer {API key} |
Content-Type | application/json-patch+json (Direct API payload) application/json (SFTP) |
Body | |
Direct API payload (JSON Patch format) | [{ "op":"add", "path":"/items/awesome_omelette_pdf", "value":{ "attributes":{ "title":"Awesome Omelette", "url":"https://www.homeoasis.com/pdf/awesome-omelette.pdf", "medium_image_url":"https://www.homeoasis.com/images/recipe/201851/img1.jpg", "rating":4.7, "category":[ "PDF", "Breakfast" ], }, "@import":{ "path":"/pdfs/awesome_omelette.pdf" } } }, { "op":"add", "path":"/items/awesome_omelette_video", "value":{ "attributes":{ "title":"How to Make Our Awesome Omelette", "url":"https://www.homeoasis.com/video/awesome-omelette-video.html", "description":"Follow along our Awesome Omelette recipe with this companion video.", "medium_image_url":"https://www.homeoasis.com/images/recipe/201851/img1.jpg", "rating":4.7, "video_id":HDRS2748, "video_duration":5, "category":[ "Videos", "Breakfast" ], }, } }] |
SFTP File (JSONLines format, file path must be relative) | [ "{catalog name}/{catalog1.jsonl}", "{catalog name}/{catalog2.jsonl}" ] |
Response | {"jobId":"713aa624-1d7c-4e4a-ac23-6463e48a5fdd"} |