Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
dev:web_api:v3:types_and_fields [2014/06/12 14:55] – created dstillman | dev:web_api:v3:types_and_fields [2019/12/06 14:51] – Clarify "conditional requests" tomas_fiers | ||
---|---|---|---|
Line 3: | Line 3: | ||
For a [[start|Zotero Web API]] client to present an editing UI to its users, it must know what combinations of Zotero item types, fields, and creator types are valid. Clients can request this data from the Zotero API. | For a [[start|Zotero Web API]] client to present an editing UI to its users, it must know what combinations of Zotero item types, fields, and creator types are valid. Clients can request this data from the Zotero API. | ||
- | As schema changes are currently rare, clients should cache type/field data for a period of time (e.g., one hour) without making further requests. Subsequent requests for new data should then include '' | + | As schema changes are currently rare, clients should cache type/field data for a period of time (e.g., one hour) without making further requests. Subsequent requests for new data should then include '' |
- | User-friendly type/field names will be returned in English by default. Clients can request names in other languages by passing a '' | + | User-friendly type/field names will be returned in English by default. Clients can request names in other languages by passing a '' |
==== Getting All Item Types ==== | ==== Getting All Item Types ==== | ||
Line 42: | Line 42: | ||
==== Getting All Valid Fields for an Item Type ==== | ==== Getting All Valid Fields for an Item Type ==== | ||
- | Note: API consumers intending to write to the server should generally use [[#get_template_for_a_new_item|/ | + | Note: API consumers intending to write to the server should generally use [[#getting_a_template_for_a_new_item|/ |
GET / | GET / |