Collections - Tier-N
Update tier-n collection settings
Changed onOverview
Update tier-n configuration for a collection. All request fields are optional (partial update). Updated settings become defaults for GET .../tier-n/data.
Validation
- Collection must exist, be active, and have tiersEnabled=true.
- maxTier 1–9 if provided; probability 0–100 if provided; dates in YYYY-MM-DD; shipmentsPeriodFrom ≤ shipmentsPeriodTo.
Audit
The update is recorded with comment "Tier-n collection settings updated via Public API".
Required Permission
manage_collection and update on the collection.
put/public/v1/collections/{collectionId}/tier-n/settings
Request
- Base URLhttps://api.prewave.com
- AuthAPI key in header X-Auth-Token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
collectionIdinteger required
Unique identifier of the tier-n collection. Same as the id from GET /public/v1/collections. The collection must have tiersEnabled=true.
Request body
Example request
{
"maxTier": 3,
"scopePrivate": true,
"scopeShared": true,
"sourceCustomer": true,
"sourceCustoms": true,
"sourcePrewavePrediction": true,
"minShipments": 5,
"probability": 75,
"shipmentsPeriodFrom": "2024-01-01",
"shipmentsPeriodTo": "2024-12-31"
}Response
Tier-n collection settings updated successfully.
Example response
{
"collectionId": 123,
"collectionName": "My Tier-N Collection",
"maxTier": 3,
"targetIds": [
101,
102,
103
],
"scopePrivate": true,
"scopeShared": true,
"sourceCustomer": true,
"sourceCustoms": true,
"sourcePrewavePrediction": true,
"minShipments": 5,
"probability": 75,
"shipmentsPeriodFrom": "2024-01-01",
"shipmentsPeriodTo": "2024-12-31",
"commodityFilterTargetIds": [
201,
202
]
}Changes
- info
request property
deprecated - info
response property
suspectedSuppliersdeprecated
- info