API documentation for the MyCirrus API
MyCirrus API - Instrument info, Data and Webhooks (1.0.1)
Request
Get weather measurements for the selected instruments and time range.
Optionally choose what period to recalculate results to.
The maximum date range per request is 31 days. If you request a longer range, the server will respond with an error.
The default Period is 1 minute.
The period can be set to anything between 1 minute and 1 day. If you request a period outside this range, the server will respond with an error.
Requires an API key with the data.enviro:read scope.
Serial numbers of selected instruments
Start date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
End date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
- Mock serverhttps://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/weather
- Production serverhttps://api.mycirrus.cloud/v1/data/weather
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/weather?instruments=QT123456%2CQT234567&start=2023-01-01T00%3A00%3A00Z&end=2023-01-31T00%3A00%3A00Z&period=PT1H' \
-H 'X-Api-Key: YOUR_API_KEY_HERE'[ { "time": "2023-06-09T01:00:00Z", "instrument": "QT123456", "windSpeed": 1.55, "windDirection": 140.37, "temperature": 10.48, "pressure": 1.012, "humidity": 82, "precipitation": 0 } ]
Request
Get particulates measurements for the selected instruments and time range.
Optionally choose what period to recalculate results to.
The maximum date range per request is 31 days. If you request a longer range, the server will respond with an error.
The default Period is 1 minute.
The period can be set to anything between 1 minute and 1 day. If you request a period outside this range, the server will respond with an error.
Requires an API key with the data.enviro:read scope.
Serial numbers of selected instruments
Start date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
End date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
- Mock serverhttps://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/particulates
- Production serverhttps://api.mycirrus.cloud/v1/data/particulates
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/particulates?instruments=QT123456%2CQT234567&start=2023-01-01T00%3A00%3A00Z&end=2023-01-31T00%3A00%3A00Z&period=PT1H' \
-H 'X-Api-Key: YOUR_API_KEY_HERE'[ { "startTime": "2023-06-08T23:00:00Z", "duration": 60, "instrument": "SCS-BGX-000", "pM1": 3.88, "pM2p5": 4.92, "pM4p25": 5.51, "pM10": 8.95 } ]
Request
Get gases measurements for the selected instruments and time range.
Optionally choose what period to recalculate results to.
The maximum date range per request is 31 days. If you request a longer range, the server will respond with an error.
The default Period is 1 minute.
The period can be set to anything between 1 minute and 1 day. If you request a period outside this range, the server will respond with an error.
Requires an API key with the data.enviro:read scope.
Serial numbers of selected instruments
Start date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
End date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
- Mock serverhttps://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/gases
- Production serverhttps://api.mycirrus.cloud/v1/data/gases
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/gases?instruments=QT123456%2CQT234567&start=2023-01-01T00%3A00%3A00Z&end=2023-01-31T00%3A00%3A00Z&period=PT1H' \
-H 'X-Api-Key: YOUR_API_KEY_HERE'[ { "startTime": "2023-06-08T23:00:00Z", "duration": 60, "instrument": "SCS-BGX-000", "co": 207.72, "cO2": 507.06, "h2S": null, "no": 0, "nO2": 19.12, "o3": null, "sO2": null, "voc": 493.25 } ]
Request
Get ground vibration measurements for the selected instruments and time range. Either Peak Particle Velocity (PPV) or Vibration Dose Value (VDV) based on the type parameter.
Optionally choose what period to recalculate results to.
The maximum date range per request is 31 days. If you request a longer range, the server will respond with an error.
The default Period is 1 minute.
The period can be set to anything between 1 minute and 1 day. If you request a period outside this range, the server will respond with an error.
Requires an API key with the data.enviro:read scope.
Serial numbers of selected instruments
Start date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
End date and time for loading a range of data. Must be in UTC.
This uses the ISO8601 format. For example, 2023-01-01T00:00:00Z is 1st January 2023 at midnight UTC.
- Mock serverhttps://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/vibration/{type}
- Production serverhttps://api.mycirrus.cloud/v1/data/vibration/{type}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.mycirrus.cloud/_mock/apis/mycirrus-main/data/vibration/{type}?instruments=QT123456%2CQT234567&start=2023-01-01T00%3A00%3A00Z&end=2023-01-31T00%3A00%3A00Z&period=PT1H' \
-H 'X-Api-Key: YOUR_API_KEY_HERE'Webhook management
Webhooks allow you to receive notifications when new data is available. You can configure webhooks via the API itself or via the console.
To create a webhook, go to the API console and click the "Create Webhook" button.
These are the endpoints you can use to manage your webhooks:
Webhook Messages
Webhooks allow you to receive notifications when new data is available. You can configure webhooks via the API itself or via the console.
To create a webhook, go to the API console and click the "Create Webhook" button.
When a webhook is triggered, a POST request will be sent to the URL you specified. The request will contain a JSON body with the data that triggered the webhook.
When processing the webhook request you must return a 200 OK response to indicate that the data was received successfully.
If a 200 response is not given or the request times out (5 seconds), the webhook will be retried up to 5 times.
To ensure a fast response we recommend you respond immediately and queue any further work to be done later.
If a webhook repeatedly fails you will be notified via email. If it continues to fail it will then be removed.
We cannot guarantee you will get a webhook request for every event so you should occasionally check for new items against the normal API endpoints. When processing events such as new measurements its also recommended to request all data since you last processed it rather than just the 1 new measurement from the request.
These are the types of webhook messages you can receive: