PUT /catalog/brands/{brand_id}/metafields/{metafield_id}
Updates a brand metafield.
Required Fields
- none
Read-Only Fields
- id
- These fields can only be modified by the app (API credentials) that created the metafield:
- namespace
- key
- permission_set
Usage Notes
- Attempting to modify
namespace,key, andpermission_setfields using a client ID different from the one used to create those metafields will result in a 403 error message. - The maximum number of metafields allowed on each order, product, category, variant, or brand is 250 per client ID. For more information, see Platform Limits in the Help Center.
Servers
- https://api.bigcommerce.com/stores/{store_hash}/v3
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
brand_id |
Integer | Yes |
The ID of the brand to which the resource belongs. |
metafield_id |
Integer | Yes |
The ID of the |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Accept |
String | Yes |
The MIME type of the response body. Default value: "application/json" |
Content-Type |
String | Yes |
The MIME type of the request body. Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
namespace |
String | No |
Namespace for the metafield, for organizational purposes. |
description |
String | No |
Description for the metafields. |
key |
String | No |
The name of the field, for example: |
permission_set |
String | No |
Determines the visibility and writeability of the field by other API consumers.
| Value | Description |
| :--- | :--- |
| Valid values:
|
value |
String | No |
The value of the field, for example: |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.