API Metafield - Revision history

Admin: /* Metafield Properties */

2020-12-16T23:49:11Z

Metafield Properties

Admin at 23:47, 16 December 2020

2020-12-16T23:47:59Z

Admin at 05:12, 23 May 2018

2018-05-23T05:12:03Z

Admin at 07:45, 22 May 2018

2018-05-22T07:45:47Z

Admin: /* Metafield Properties */

2018-05-22T03:25:54Z

Metafield Properties

Admin at 02:23, 22 May 2018

2018-05-22T02:23:11Z

Admin at 02:21, 22 May 2018

2018-05-22T02:21:52Z

Admin at 01:49, 22 May 2018

2018-05-22T01:49:29Z

Show changes

Admin at 01:44, 22 May 2018

2018-05-22T01:44:02Z

Admin: /* PUT /api/metafields/METAFIELD_ID.jsonPUT /api/products/PRODUCT_ID/metafields/METAFIELD_ID.jsonPUT /api/variations/VARIATION_ID/metafields/METAFIELD_ID.jsonPUT /api/pages/PAGE_ID/metafields/METAFIELD_ID.jsonPUT /api/blogs/BLOG_ID/metafields/META...

2015-02-20T01:20:59Z

/* PUT /api/metafields/METAFIELD_ID.jsonPUT /api/products/PRODUCT_ID/metafields/METAFIELD_ID.jsonPUT /api/variations/VARIATION_ID/metafields/METAFIELD_ID.jsonPUT /api/pages/PAGE_ID/metafields/METAFIELD_ID.jsonPUT /api/blogs/BLOG_ID/metafields/META...

@@ Line 107: / Line 107: @@
 !value_type
 |<pre>{ "value_type" : "string" }</pre>
-The metadata value can be treated as either a ''string'' or an ''integer''.
+The metadata value can be treated as either a ''string'', ''integer'' or ''json_string''.
 |-
 !description

@@ Line 18: / Line 18: @@
 * Key
 * Value
-* Value Type (''integer'' or ''string'')
+* Value Type (''integer'', ''string'' or ''json_string'')
 * Description (Optional)
-The Namespace allows you to group a number of related keys together. Within a namespace, there will be one or more unique keys. Each key within the namespace will have a value which may be either an ''integer'' or ''string'' value.
+The Namespace allows you to group a number of related keys together. Within a namespace, there will be one or more unique keys. Each key within the namespace will have a value which may be either an ''integer'', ''string'' or ''json_string'' value.
 Finally, for documentation purposes, an optional Description may also be added when the Metafield is created.

← Older revision		Revision as of 05:12, 23 May 2018
Line 1:		Line 1:
−	~~<html>~~	+	The Spiffy Stores API Metafield reference allows you to attach metadata to a number of your store's objects.
−	~~<style type="text/css">~~
−	~~table.reference {~~
−	~~width: 100%;~~
−	~~border: 1px solid #c9c9c9;~~
−	}
−	~~table.reference th, table.reference td {~~
−	~~border: 1px solid #c9c9c9;~~
−	~~padding: 10px;~~
−	}
−	~~table.reference th {~~
−	~~text-align: left;~~
−	~~vertical-align: top;~~
−	~~width: 30%;~~
−	~~font-size: 100%;~~
−	}
−	~~table.reference td pre {~~
−	~~margin: 10px 0px;~~
−	~~font-size: 80%;~~
−	~~display: block;~~
−	}
−	~~pre {~~
−	~~width: 100%;~~
−	}
−	~~</style>~~
−	~~</html>~~
−
−	The Spiffy Stores API Metafield ~~object~~ allows you to attach metadata to a number of your store's objects.

	In this context, metadata represents any sort of data that can be represented by a ''key/value'' structure and can be associated with one of the following types of store objects.		In this context, metadata represents any sort of data that can be represented by a ''key/value'' structure and can be associated with one of the following types of store objects.

@@ Line 19: / Line 19: @@
        font-size: 80%;
        display: block;
+     }
    </style>
@@ Line 369: / Line 372: @@
 {}
 </pre>

@@ Line 119: / Line 119: @@
 !namespace
 |<pre>{ "namespace" : "accessories" }</pre>
-This is the name assigned to a set of unique metadata keys. Namespaces allow you to group and manage the metadata associated with the objects. A Namespace name has a maximum of 20 characters.
+This is the name assigned to a set of unique metadata keys. Namespaces allow you to group and manage the metadata associated with the objects. A Namespace name has a maximum of 20 lower-case alphabetic characters, numbers and '_'.
 |-
 !key

@@ Line 23: / Line 23: @@
 </html>
-The Spiffy Stores API Metafield object allows you to attach metadata to a number of your Store's objects.
+The Spiffy Stores API Metafield object allows you to attach metadata to a number of your store's objects.
 In this context, metadata represents any sort of data that can be represented by a ''key/value'' structure and can be associated with one of the following types of store objects.

@@ Line 1: / Line 1: @@
 The Spiffy Stores API Metafield object allows you to attach metadata to a number of your Store's objects.
@@ Line 92: / Line 116: @@
 == Metafield Properties ==
-<html>
+{| class="reference"
-  <style type="text/css">
+!id
 |<code>{ "id" : 123456789 }</code><br/>
 A unique numeric identifier for the metafield.

← Older revision		Revision as of 01:20, 20 February 2015
Line 339:		Line 339:

	HTTP/1.1 200 OK		HTTP/1.1 200 OK
		+	</pre>
		+
		+	=== <code>DELETE /api/metafields/METAFIELD_ID.json<br/>DELETE /api/products/PRODUCT_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/variations/VARIATION_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/pages/PAGE_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/blogs/BLOG_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/standard_collections/STANDARD_COLLECTION_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/super_collections/SUPER_COLLECTION_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/customers/CUSTOMER_ID/metafields/METAFIELD_ID.json<br/>DELETE /api/orders/ORDER_ID/metafields/METAFIELD_ID.json</code> ===
		+
		+	Delete an existing metafield that belongs to the store, product, variation, page, blog, standard collection, super collection, customer or order.
		+
		+	==== Example Request and Response ====
		+
		+	<pre>
		+	DELETE /api/metafields/123456789.json
		+
		+	HTTP/1.1 200 OK
		+
		+	{}
	</pre>		</pre>