Arable Backend API 3.7.0 Release Notes

Doc Number: ARA2023-00001 Rev A Date: May 01, 2023

Release Overview

Arable API 3.7.0 is a release supporting the Arable Mark 3.

Main endpoints supported for the Arable Developer API are listed in this file.

We hope you will enjoy this new release. We always welcome your feedback through Customer Success ( or via your account manager. 


May 01,  2023

Instance affected



api-device v1.17.0

api-user v3.45.2

data-processing v0.31.0

api-weather v2.22.0

app-admin 1.19.0

postgresDB 12.0.0




3rd Party Sensors

Sentek Drill and Drop Soil Moisture Probe DD-MTS and DD-MT

Davis Wind Anemometer 6410 and 7911

GEMS PS41 Series Pressure Switch

Type of Release

Minor Release




List of Changes

New Features


Delayed Data Notification Service via Webhook interface

Aligned Weather Data Aggregation for Hourly and Daily table in the data API

  1. Aggregated measurement of “max_rh” for daily, hourly, and (local_hourly).
  2. Aggregate measurement of  “rh_at_mint” for hourly and (local_hourly).

Defect Fixes


Update the AUX Bridge and the Connected Sensor Status in Mark 2 to present the true operational status of the bridge electrical connection and sensor data flow to the users/admin in the App UI.

Fix the wind speed data from“null” to “0” in case of zero wind in that aggregation period. If the aggregated value is still null, then we will change this to zero wind speed. This was deemed acceptable given the trade-off with lots of nulls today for zero wind. 

Known Issues


While the API documentation at is helpful, it is auto-generated and is missing a list of all available endpoints. We will add this into the Guide section in the future. In the meantime, if you need more help related to understanding the endpoints available on each API route, please review this file or contact Arable Customer Success via the Help icon in your app. 

It can take several minutes (up to an hour) to see measurement data after a new installation if the unit was not properly undeployed after the previous installation, as data will have been collected during transport and the Mark will send its data in FIFO mode. 

If GPS isn't available at a deployment (e.g., deployed indoors), the deployment may fail with a server-side exception. It is important to note that the Arable system is currently based on the availability of GPS in order to provide accurate locations on maps and in calculations. We are looking into how we can operate better with adding the GPS coordinates via the API (and UI) if not automatically reported by the Arable Mark 2.