PUT | /customfieldsbatch | Updates or Creates a Custom Field Value for multiple products, up to 500 |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CustomFieldRequests | body | List<CustomFieldRequest> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ProductId | form | int | No | |
CustomFields | form | List<CustomFieldRequestModel> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CustomFieldId | form | int | No | |
DisplayName | form | string | No | |
Value | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No | |
Errors | form | List<string> | No | |
Warnings | form | List<string> | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /customfieldsbatch HTTP/1.1
Host: avb-pos.avbportal.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"customFieldRequests":[{"productId":0,"customFields":[{"customFieldId":0,"displayName":"String","value":"String"}]}]}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}},"errors":["String"],"warnings":["String"]}