Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
dev:web_api:v2:changes_from_v1 [2013/02/12 19:47] dstillmandev:web_api:v2:changes_from_v1 [2013/02/27 23:27] fcheslack
Line 13: Line 13:
   * Object ETags have been replaced by [[syncing#version_numbers|library/object versions]]. ''If-Match'' has been replaced by ''If-Unmodified-Since-Version'' and JSON version properties.   * Object ETags have been replaced by [[syncing#version_numbers|library/object versions]]. ''If-Match'' has been replaced by ''If-Unmodified-Since-Version'' and JSON version properties.
   * Object writes no longer return Atom feeds with the newly created objects. Single-object writes return ''204 No Content'', while [[write_requests#creating_multiple_objects|multi-object writes]] return ''200 OK'' with a JSON document indicating the status of each write.   * Object writes no longer return Atom feeds with the newly created objects. Single-object writes return ''204 No Content'', while [[write_requests#creating_multiple_objects|multi-object writes]] return ''200 OK'' with a JSON document indicating the status of each write.
-  * ''X-Zotero-Write-Version'' has changed to ''Zotero-Write-Version''.+  * ''X-Zotero-Write-Token'' has changed to ''Zotero-Write-Token''.
   * Child items can no longer be created by including ''note'' or ''attachment'' properties when creating top-level items or by POSTing to ''<userOrGroupPrefix>/items/<itemKey>/children''. Instead, child items can be created or moved by including a ''parentItem'' property in the item's JSON.   * Child items can no longer be created by including ''note'' or ''attachment'' properties when creating top-level items or by POSTing to ''<userOrGroupPrefix>/items/<itemKey>/children''. Instead, child items can be created or moved by including a ''parentItem'' property in the item's JSON.
   * New collection JSON objects can no longer be POSTed directly. Instead, collections must be within a top-level ''collections'' object, similar to the ''items'' object used for items.    * New collection JSON objects can no longer be POSTed directly. Instead, collections must be within a top-level ''collections'' object, similar to the ''items'' object used for items. 
   * The ''parent'' property for collections has been changed to ''parentCollection''.   * The ''parent'' property for collections has been changed to ''parentCollection''.
   * The collections an item belongs to can be read and modified via the item's ''collections'' property. The previous POST and DELETE requests have been removed.   * The collections an item belongs to can be read and modified via the item's ''collections'' property. The previous POST and DELETE requests have been removed.
dev/web_api/v2/changes_from_v1.txt · Last modified: 2017/11/27 04:20 by bwiernik