# Mithra Public API

## Docs
- [Mithra Public API](https://api.mithra.network/docs/mithra-public-api-1259112m0.md): 
- Realtime (SSE) [SSE Event Schema](https://api.mithra.network/docs/sse-event-schema-1263022m0.md): 

## API Docs
- Realtime (SSE) [Connect (SSE)](https://api.mithra.network/docs/connect-sse-18946438e0.md): A simple GET call to this endpoint will start a SSE session. You will obtain your `clientId`, so you can setup your subscriptions.
- Realtime (SSE) [Subscribe (SSE)](https://api.mithra.network/docs/subscribe-sse-18946502e0.md): After connecting & thus obtaining your subscription's `clientId` you can subscribe to topics.
- [List Sensors](https://api.mithra.network/docs/list-sensors-18858186e0.md): List all sensors, metadata and their `id` (which is the `sensor_id` for other sensor related API calls) and `location` (which is the idea corresponding to the `id` field in location related API's).
- [List Locations](https://api.mithra.network/docs/list-locations-18864657e0.md): List all locations (sensor location details)
- [Sensor Readings](https://api.mithra.network/docs/sensor-readings-18860423e0.md): Get the details of a sensor, including current readings. To fetch more data, use the last record's `moment` unix timestamp and include it in the next call as query param `after_timestamp` to fetch the next page of records. If you are persisting records in your own application, you can obviously stop fetching for more records when the last record's `moment` unix timestamp exceeds the record(s) you already have.