API Reference
The Attlaz API is used for submitting events to the Attlaz collector as well as exporting and managing data.
Versioning
Versioned changes are changes introduced with the release of a new API version. Versioned changes typically apply to the newest version immediately and often will apply to other versions at a future date. The changelog accompanying each release indicates which changes apply to the current release and which changes apply to other versions.
| Version | Date introduced | Available Until |
|---|---|---|
| beta | - | - |
| 1.12 | November 2024 | TBD |
| 1.11 | January 2024 | TBD |
| 1.10 | November 2023 | TBD |
| 1.9 | January 2023 | December 2024 |
| 1.8 | April 2022 | December 2023 |
| 1.7 | March 2022 | December 2022 |
| 1.6 | February 2022 | December 2022 |
| 1.5 | January 2022 | December 2022 |
| 1.4 | January 2022 | December 2022 |
| 1.3 | January 2022 | December 2022 |
| 1.2 | March 2021 | December 2022 |
| 1.1 | March 2019 | December 2021 |
| 1.0 | April 2017 | December 2021 |
The current version of the web API is known as 1.12 and is considered to be in a draft phase. While we don’t expect public endpoints to change greatly, keep in mind that the API is still under development.
The endpoint of the API is following scheme:
https://api.attlaz.com/{version}
It is possible to not pass a version, then the endpoint point to the latest stable version, however this is not advices.
curl -i -X "https://api.attlaz.com/1.12/
The same unversioned call is as follows:
curl -i -X "https://api.attlaz.com/stable/
An unversioned call uses the latest stable version of the API.
It is possible to always use the beta version of the API:
curl -i -X "https://api.attlaz.com/beta/