Skip to main content

Update an extra suboption metafield

API operation: Open the endpoint in Scalar

Use PUT /business/{business_id}/extras/{extra_id}/options/{option_id}/suboptions/{suboption_id}/metafields/{metafield_id} to update one metafield on an extra suboption. The operation is ExtraOptionSuboptionMetafield.update.

The identifiers are hierarchical: metafield_id must belong to the specified suboption_id, which belongs to option_id, extra_id, and business_id. The route identifies the literal model as ExtraOptionSuboption and the metafield object ID from the route.

The endpoint validates value according to value_type; supported value_type values are integer, decimal, boolean, text, and json. The key requirement and validation may differ between creation and update.

The operation requires administrator or business-manager authentication and scopes business managers through associated businesses.

See find an extra suboption metafield for the item read.

OpenAPI reference​

Operation: PUT /business/{business_id}/extras/{extra_id}/options/{option_id}/suboptions/{suboption_id}/metafields/{metafield_id}

Path parameters

NameTypeRequiredDescription
business_idintegerYes—
extra_idintegerYes—
option_idintegerYes—
suboption_idintegerYes—
metafield_idintegerYes—

Request body fields

NameTypeRequired
keystringNo
modelanyYes
object_idintegerNo
valueanyNo
value_typestringNo

Responses

CodeDescription
200OK (Envelope)
400Bad Request (ErrorResponse)
401Unauthorized
404Not Found
429Too Many Requests (ErrorResponse)
500Internal Server Error (ErrorResponse)
503Service Unavailable (ErrorResponse)
Open this operation in the API reference