ICOS Data Usage Statistics: the API

The API

Every endpoint of the download statistics lives under /stats/api/ and answers JSON, by GET with a query string or by POST with a JSON object carrying the same names; OPTIONS answers the CORS preflight. The same table, as a machine-readable document: openapi.json, with the keys below as the parameters of every endpoint; browse and try them in Swagger UI.

The query

A list key takes repeated keys (specs=A&specs=B), a comma list (specs=A,B) or a JSON array literal (specs=%5B%22A%22%5D); in a POST body the same names carry JSON arrays. Every key is optional; an endpoint ignores the keys it has no use for. A value that cannot be read is answered 400 with the key named. Answers to the filtered endpoints are cached for ten minutes.

Examples

GET /stats/api/downloadsPerYear?dlfrom=SE
GET /stats/api/downloadsByCountry?specs=http://meta.icos-cp.eu/resources/cpmeta/atcCo2L2DataObject&dlStart=2024-01-01
GET /stats/api/downloadCount?hashId=0iQnqctEYJ-jM0ERHkXmVUO8
POST /stats/api/downloadStats
Content-Type: application/json

{"dlfrom":["SE","DE"],"dlStart":"2024-01-01","pagesizeOpt":10}

GET /stats/csv?unit=month&dlfrom=SE

The pages

The same statistics as pages, every filter in the URL under the keys above; the CSV routes answer the series of the page.