Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
dev:web_api:v2:read_requests [2014/07/05 11:46]
dstillman [URL Parameters] correct max limit (100, not 99)
dev:web_api:v2:read_requests [2017/11/12 19:53]
127.0.0.1 external edit
Line 1: Line 1:
 +<​html><​p id="​zotero-5-update-warning"​ style="​color:​ red; font-weight:​ bold">​We’re
 +in the process of updating the documentation for
 +<a href="​https://​www.zotero.org/​blog/​zotero-5-0">​Zotero 5.0</​a>​. Some documentation
 +may be outdated in the meantime. Thanks for your understanding.</​p></​html>​
 +
 +
 ====== Zotero Server Read Requests ====== ====== Zotero Server Read Requests ======
  
Line 15: Line 21:
 ===== API Versioning ===== ===== API Versioning =====
  
-**To use this version of the API, include the HTTP header ''​Zotero-API-Version:​ 2''​ with all requests.** The current default version is [[:​dev/​web_api/​v1/​|version ​1]], which will be discontinued in the near future.+To use this version of the API, include the HTTP header ''​Zotero-API-Version:​ 2''​ with all requests. **The current default version is [[:​dev/​web_api/​v3/​|version ​3]].**
  
 At most times, there is only one active API version, and changes are made in a backwards-compatible manner. On rare occasions, however, backwards-incompatible changes may need to be made. When this occurs, the new API version will first be made available via an HTTP header, ''​Zotero-API-Version:​ <​version>'',​ while all other clients continue to receive the old version. After a transition period, the new API version will become the default. At that point, the previous API version may be discontinued,​ with the new API version being returned even to clients requesting the previous version. Announcements regarding API version transitions will always be made ahead of time on [[https://​groups.google.com/​group/​zotero-dev|zotero-dev]]. At most times, there is only one active API version, and changes are made in a backwards-compatible manner. On rare occasions, however, backwards-incompatible changes may need to be made. When this occurs, the new API version will first be made available via an HTTP header, ''​Zotero-API-Version:​ <​version>'',​ while all other clients continue to receive the old version. After a transition period, the new API version will become the default. At that point, the previous API version may be discontinued,​ with the new API version being returned even to clients requesting the previous version. Announcements regarding API version transitions will always be made ahead of time on [[https://​groups.google.com/​group/​zotero-dev|zotero-dev]].
dev/web_api/v2/read_requests.txt · Last modified: 2017/11/27 04:16 by bwiernik