Metafield Input
The input fields to use to create or update a metafield through a mutation on the owning resource. An alternative way to create or update a metafield is by using the metafieldsSet mutation.
Anchor to FieldsFields
- •ID
The unique ID of the metafield. Using
,
namespace
, andkey
is preferred for creating and updating.- •String
The unique identifier for a metafield within its namespace.
Required when creating a metafield, but optional when updating. Used to help identify the metafield when updating, but can't be updated itself.
Must be 2-64 characters long and can contain alphanumeric, hyphen, and underscore characters.
- Anchor to namespacenamespace•String
The container for a group of metafields that the metafield is or will be associated with. Used in tandem with
key
to lookup a metafield on a resource, preventing conflicts with other metafields with the samekey
.Required when creating a metafield, but optional when updating. Used to help identify the metafield when updating, but can't be updated itself.
Must be 3-255 characters long and can contain alphanumeric, hyphen, and underscore characters.
- Anchor to typetype•String
The type of data that is stored in the metafield. Refer to the list of supported types.
Required when creating or updating a metafield without a definition.
- Anchor to valuevalue•String
The data stored in the metafield. Always stored as a string, regardless of the metafield's type.
- Anchor to descriptiondescription•StringDeprecated
Anchor to Input objects using this inputInput objects using this input
- •INPUT OBJECT
The input fields to create an article.
- •INPUT OBJECT
The input fields to update an article.
- •INPUT OBJECT
The input fields to create a blog.
- •INPUT OBJECT
The input fields to update a blog.
- •INPUT OBJECT
The input fields required to create a collection.