Getting Started with the Conserv API

The Conserv Public API gives you programmatic access to your environmental monitoring data — sensor readings, observations, events, and more — for integration with your own systems and workflows.

Base URL

Environment	URL
Production	https://api.conserv.io/
Staging	https://staging.api.conserv.io/
Development	https://dev.api.conserv.io/

Authentication

All API requests require an API key issued by Conserv. Pass the key in the x-api-key request header:

GET /v1/sensors HTTP/1.1
Host: api.conserv.io
x-api-key: YOUR_API_KEY

To obtain an API key, customers can contact support.

Your First Request

Retrieve all sensors in your account:

curl https://api.conserv.io/v1/sensors \
  -H "x-api-key: YOUR_API_KEY"

Data Model

Customer
  └── Facility (Location)
        └── Zone (Space)
              └── Sensor
                    └── Readings / Observations

All data returned by the API is scoped to the customer associated with your API key.

Response Format

All endpoints return JSON. Successful responses use HTTP 200 OK. Errors follow standard HTTP status codes with a JSON body:

{
  "error": "Unauthorized",
  "message": "Invalid or missing API key"
}

Rate Limits

Rate limiting details will be published here. Contact support if you need higher throughput.

Pagination

The /events and /observations endpoints support page-based pagination via page query parameter. Responses include a pagination object with page and pageSize fields. See the API Reference for details.

Next Steps

• Browse the full API Reference
• Use GET /sensors to list your sensors
• Use GET /sensors/{sensorId}/data to pull time-series readings