---
title: "POST /catalog/brands/{brand_id}/metafields"
method: POST
path: "/catalog/brands/{brand_id}/metafields"
tags: ["Catalog"]
---

# POST /catalog/brands/{brand_id}/metafields

`POST /catalog/brands/{brand_id}/metafields`

Creates a product `Metafield`.

## Request body

- MetafieldPost — Common Metafield properties.
  - `permission_set` 'app_only' | 'read' | 'write' — Determines whether the field is completely private to the app that owns the field (`app_only`), or visible to other API consumers (`read`), or completely open for reading and writing to other apps (`write`).
  - `namespace` string — Namespace for the metafield, for organizational purposes.
  - `key` string — The name of the field, for example: `location_id`, `color`.
  - `value` string — The value of the field, for example: `1`, `blue`.
  - `description` string — Description for the metafields.
  - `resource_type` 'category' | 'brand' | 'product' | 'variant' — The type of resource with which the metafield is associated.
  - `resource_id` integer — The unique identifier for the resource with which the metafield is associated.

## Response `200`

A `Metafield` object.

- MetafieldResponse — Response payload for the BigCommerce API.
  - `data` Metafield — Common Metafield properties.
    - `permission_set` 'app_only' | 'read' | 'write' — Determines whether the field is completely private to the app that owns the field (`app_only`), or visible to other API consumers (`read`), or completely open for reading and writing to other apps (`write`).
    - `namespace` string — Namespace for the metafield, for organizational purposes.
    - `key` string — The name of the field, for example: `location_id`, `color`.
    - `value` string — The value of the field, for example: `1`, `blue`.
    - `description` string — Description for the metafields.
    - `resource_type` 'category' | 'brand' | 'product' | 'variant' — The type of resource with which the metafield is associated.
    - `resource_id` integer — The unique identifier for the resource with which the metafield is associated.
    - `id` integer — The unique identifier for the metafields.
    - `created_at` string, date-time — Date and time of the metafield's creation.
    - `updated_at` string, date-time — Date and time when the metafield was last updated.
  - `meta` Meta — Empty meta object; may be used later.

## Other responses

- `409` — The `Metafield` was in conflict with another `Metafield`. This can be the result of duplicate unique key combination of the app's client id, namespace, key, resource_type, and resource_id.
- `422` — The `Metafield` was not valid. This is the result of missing required fields, or of invalid data. See the response for more details.

---

[API](https://skmtc.dev/bigcommerce/apis/bigcommerce-api.md) · [All operations](https://skmtc.dev/bigcommerce/apis/bigcommerce-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/bigcommerce/bigcommerce-api/revisions/90efb67b99f3/schema)