Create Multiple Metafields
Create multiple metafields.
Authentication
X-Auth-Tokenstring
### OAuth scopes
| UI Name | Permission | Parameter |
|:--------|:-----------|:----------|
| Products | modify | `store_v2_products` |
| Products | read-only | `store_v2_products_read_only` |
### Authentication header
| Header | Argument | Description |
|:-------|:---------|:------------|
| `X-Auth-Token` | `access_token` | For more about API accounts that generate `access_token`s, see our [Guide to API Accounts](/developer/docs/overview/api-accounts#api-accounts). |
### Further reading
For example requests and more information about authenticating BigCommerce APIs, see [Authentication and Example Requests](/developer/docs/overview/api-accounts#x-auth-token-header-example-requests).
For more about BigCommerce OAuth scopes, see our [Guide to API Accounts](/developer/docs/overview/api-accounts#oauth-scopes).
For a list of API status codes, see [API Status Codes](/developer/api-reference/rest/overview#rest-http-status-codes).
Request
key
The name of the field, for example: location_id, color.
namespace
Namespace for the metafield, for organizational purposes.
permission_set
Determines the visibility and writeability of the field by other API consumers.
| Value | Description |
| :--- | :--- |
| `app_only` | Private to the app that owns the field. |
| `read` | Visible to other API consumers. |
| `write` | Open for reading and writing by other API consumers. |
| `read_and_sf_access` | Visible to other API consumers, including on the storefront. |
| `write_and_sf_access` | Open for reading and writing by other API consumers, including on the storefront. |
Allowed values:
resource_id
The ID for the product with which the metafield is associated.
value
The value of the field, for example: 1, blue.
description
Description for the metafields.
Response
List of created Metafield objects.
data
errors
Empty for 200 responses.
meta
Additional data about the response.
Errors
400
Bad Request Error
422
Unprocessable Entity Error
