API changelog

0.4.0 – September 1, 2024

  • We deprecated legacy endpoint for pushing data and introduced a new one that is also supported in updated SDKs.
  • The change introduced is backward compatible, therefore all existing custom push integrations are not affected until further notice.
  • We encourage everyone to switch to the new /data endpoint using more flexible data structures.

0.3.12 – June 19, 2023

  • Returning more descriptive and meaningful message back to user, when validating the request. Read more about new error responses here.

0.3.5 – April, 2023

  • Performance improvements and bug fixes.
  • Removed support for making requests with the use of TLS 1.0 and TLS 1.1 security protocols (both protocols officially deprecated by IETF on March 2021).

0.3.0 – December 10, 2022

  • Removed support for ensureUnique flag sent with the push payload. This flag will be ignored. To store multiple values to the same timestamp there is new Metric definition option “Store all values, even if Date/Time is an exact match to another entry”. Read more about this optional setting here.

0.2.3 – October 14, 2022

  • Fixed value validation to not count the decimal separator character as an additional digit
  • Added validation for metric key names. The metric key name must start with the dollar ($) sign

0.2.2 – August 27, 2022

  • Added validation for metric values. Whole numbers can be up to 16 digits long. When storing decimal values (using the decimal separator “.”), up to 6 decimal digits are supported.
  • Added validation for dimension and metric key names. The name fields are case sensitive and you can use any alphanumeric value (a-z, A-Z, 0-9, _).

0.2.0 – August 24, 2022

  • Added support for ensureUnique flag. Read more about this optional setting here.