Sensor Configuration History

The /sensor-configuration-history url returns the history of Smart Mooring sensor configurations reported by a deployed Spotter within a given date-time window.

Smart Mooring Sensor Configuration History

GET https://api.sofarocean.com/api/sensor-configuration-history?spotterId=:spotterId&startDate=:startDate&endDate=:endDate

Returns Smart Mooring sensor configurations for the corresponding spotterId between startDate and endDate.

circle-info

Note: This API endpoint will only return sensor configuration history since June, 2025.

Query Parameters

Name
Type
Description

spotterId

string

SpotterId of the device to retrieve data for.

startDate

string

ISO8601-formatted timestamp string indicating start date for data inclusion. Example: 2025-01-01T07:00:00Z

endDate

string

ISO8601-formatted timestamp string indicating end date for data inclusion. Example: 2025-01-02T07:00:00Z

Example Request

curl "https://api.sofarocean.com/api/sensor-configuration-history?spotterId=SPOT-0222&startDate=2025-12-01T07:00:00Z&endDate=2025-12-02T07:00:00Z" -H 'token: YOUR_API_TOKEN'

Response Description

To learn more about the sensors and the measured data please review our Sensor Payload support documentarrow-up-right.

Each element of the data array represents a complete configuration of all sensors attached to the Smart Mooring at one time.

timestamp is an ISO8061-formatted string representing the time the configuration was reported by the Spotter, and it was in effect for all data samples collected until the following sensor configuration entry. If a sensor configuration was in use prior to the startTime query parameter passed in, the first entry will have the timestamp of the first sensor datum at or after startTime, not the earliest time the configuration was used.

configuration_checksum is a checksum unique to a given mooring configuration. If the Smart Mooring sensors are changed, but then later returned to an earlier configuration, the configuration_checksum will be the same, assuming the sensors are in the same positions and have the same setting configured. The configuration_checksum returned with sensor data samples from /sensor-data can be cross-referenced with this field to determine the sensor configuration with which the sample was collected.

The sensor_configurations array contains details of the configuration of each sensor:

  • sensor_type describes the type of sensor.

  • position is the physical position of a sensor in the Smart Mooring relative to Spotter. Position 1 is closest to Spotter, and position 0 is the Bristlemouth processor within the Spotter buoy at the root of the Smart Mooring.

  • configuration describes configuration settings for the sensor.

  • data_types describes the data fields and units potentially returned by the sensor among its data samples.

  • firmware_sha and bristlemouth_node_id refer to the Bristlemouth mote within the sensor.

Example Response

Last updated

Was this helpful?