Consistent casing
In general, the following conventions now apply:
Usage | Convention | Example |
---|---|---|
Query parameters | camelCase | {"activityUnit" : "$US", "activityClassificationSystem": "GLORIA"} |
Returned fields | camelCase | "impactCategory":"GHG Total" |
Endpoints | hyphenated | /impact-category |
Batch requests
It is now possible to submit multiple search queries in a single request (up to 50).
Impact calculation
You can now pass an optional activityMeasure
value (a number) to a search endpoint and receive a calculation of the total impact.
Attenuate fields option
If desired, you can pass a fields_returned
parameter with a search query to reduce the volume of data sent back.