Cryosphere REST API

The Cryosphere Innovation REST API gives programmatic, cross-platform access to the Cryosphere Innovation system. Query deployment metadata and raw sensor data from any programming language that speaks HTTP — responses come back as JSON you can parse into native objects.

A quick look

The API is designed to be easy to try. With a valid API key, this Python snippet fetches metadata for every public deployment:

quickstart.py
import requests
 
url = "https://api.cryosphereinnovation.com/public/deployments/"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
 
response = requests.get(url, headers=headers).json()
print(response["results"])
quickstart.py
import requests
 
url = "https://api.cryosphereinnovation.com/public/deployments/"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
 
response = requests.get(url, headers=headers).json()
print(response["results"])

Any language with HTTP support — Python, MATLAB, JavaScript, C/C++, Arduino — will work the same way.

What you can do

  • Fetch deployment metadata — names, locations, start dates, status, and owner-supplied details
  • Fetch raw sensor data — temperature strings, GPS, pressure, CTD, battery, and every other channel an instrument reports
  • Filter, search, sort, and paginate the deployments list
  • Read both public and private deployments that you own or collaborate on

If you need to push data into Cryosphere Innovation (instead of read from it), see the Data Platform docs — the public API is read-only.

Endpoints at a glance

All requests are made against a single base URL:

https://api.cryosphereinnovation.com
EndpointPurpose
/public/deployments/Deployment metadata — list all deployments or fetch one by slug
/public/deployment/data/{uuid}Raw sensor data for a single deployment

See the full reference, including every query parameter and response field, on the Endpoints page.

Access model

Public data. Every deployment listed in our Data Portal is readable via the API with any valid key.

Private data. Deployments marked private are only visible to the instrument owner and listed collaborators. API access follows the same rules.

Continue reading

The next pages in this section walk through the API in depth:

  1. Quickstart — go from zero to your first request in five minutes
  2. Authentication — API keys, private-deployment access, and browser access
  3. Endpoints — complete reference for every URL, parameter, and response field
  4. Fetching deployments — filter, search, sort, and paginate the deployments list
  5. Fetching sensor data — query raw time-series readings for a deployment
  6. Errors — HTTP status codes, response bodies, and retry guidance