Get Customizations
POSTOverview
Section titled “Overview”Retrieve a list of existing recommendation customizations. This endpoint supports pagination through query parameters and additional filtering through query parameters or a criteria object in the request body.
Request parameters
Section titled “Request parameters”Send a POST request with the tracker_id in the path. Pagination and simple filters go in the query string.
Path parameters
Section titled “Path parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
TRACKER_ID | string | ✓ | Your unique tracker identifier. |
Query parameters
Section titled “Query parameters”| Parameter | Type | Description |
|---|---|---|
limit | integer | Number of customizations to return. |
offset | integer | Number of results to skip. |
model | array[string] | Filter by recommender model, for example model=basket&model=home. |
tag | array[string] | Filter by tags. |
target_type | array[string] | Filter by scope type: item, criteria, or all. |
target_identity | array[string] | Filter by specific target item IDs. |
sort | array[string] | Sort by attribute, for example created_at:desc. |
Request headers
Section titled “Request headers”| Header | Value | Description |
|---|---|---|
Content-Type | application/json; charset=utf-8 | Required. |
Date | HTTP date | Required for HMAC. |
Authorization | ApiAuth {TRACKER_ID}:{SIGNATURE} | Required for HMAC. |
Request body
Section titled “Request body”The body accepts a JSON object with a criteria array for advanced filtering. The criteria structure follows the same rules described in Recommendations Customization.
How to Make a Request
Section titled “How to Make a Request”All requests to this endpoint must be authenticated with HMAC SHA-256.
- Build the string to sign from the HTTP method, content type, current date, and the resource path.
- Exclude query parameters from the signed path for this endpoint.
- Generate the Base64-encoded signature with your private key.
- Send the request with
Date,Content-Type, andAuthorizationheaders.
Response structure
Section titled “Response structure”The response contains pagination metadata and the list of matching customization objects.
Response attributes
Section titled “Response attributes”| Field | Type | Description |
|---|---|---|
pagination | object | Metadata about the result set. |
pagination.total | integer | Total number of items matching the filter. |
results | array | List of customization objects. |
Error handling
Section titled “Error handling”| HTTP Status | Description |
|---|---|
200 OK | Success. |
401 Unauthorized | Missing or invalid authentication. |
404 Not Found | Tracker not found. |
422 Unprocessable Entity | Validation error, for example an invalid sort field. |
Was this page helpful?
Thanks.