Metafield specification
If you are querying the list of the metafields (REST API) instead single metafield, you can find our metafield by filtering the list by attributes:
The namespace and key pair are unique. There will be always one or zero, never more.
Metafield object contains value
attribute which is always a JSON String.
Example response from Admin REST API:
Parsed example:
The structure of the JSON object is as follows:
Attribute | Type | Description |
---|---|---|
provider | String | Points provider, typically carrier name |
code | String | Carrier given identifier |
details | Details object | Pickup point details |
address | Address object | Pickup point address |
attributes | Attributes object[] | List of pickup point attributes - varies by carrier |
Details object
Attribute | Type | Description |
---|---|---|
name | String | Name of the pickup point |
description1 | String | Description |
description2 | Nullable String | Second line of the description |
distance | String | Human readable distance in local format |
Address object
Attribute | Type | Description |
---|---|---|
address1 | String | First line of the address |
address2 | Nullable String | Second line of the address |
city | String | City |
zip | String | Postal code |
province | Nullable String | Province name |
provinceCode | Nullable String | Province code |
countryCode | String | Country code ISO 3166-1 alpha-2 |
Attributes object
Attribute | Type | Description |
---|---|---|
key | String | Key of the attribute |
value | String / Boolean / Number | Value of the attribute |