Bulk resource attribute values by resource lookup key
POST/:resourceType/:lookupKey/:lookupValue/attributes
The bulk resource attribute endpoint sets/ deletes resource attributes for a single resource identified by the lookup key. The attribute is identified via the payload by providing either id or name. If both are provided, id will be used to identify the attribute. Below is a summary of all the possible fields in the payload.
Fields
| Name | Required |
|---|---|
id | yes, if name not provided |
name | yes, if id not specified |
class | yes, if id not specified |
type | yes |
value | no, if omitted the attribute value will be deleted for the resource (set to default) |
A successful response contains data about each attribute changes: whether the attribute was created/ updated for that resource, in which case the action in the response will be put, or delete if the value of the attribute for the particular resource is being deleted. After it is deleted, the attribute value for the specific resource will inherit the value from the parent resource(s).
In case of an issue, the data will contain a message explaining the reason, for ex. when an attribute is not found, or the value provided does not match the attribute type, etc.
Request
Responses
- 200
- 400
- 404
Bulk product attribute values by product id - 200 / Bulk product attribute values by product source id - 200 / Bulk user attribute values by user id and attribute name - 200
Response Headers
Bulk product attribute values by product id - 400 (schema validation error)
Response Headers
Bulk product attribute values by product id - 404 / Bulk product attribute values by product source id - 404