Introduction

The Traces API is organized around REST architectural style. Our API has predictable resource-oriented URLs, JSON-encoded responses, standard HTTP response codes, and key-based authentication.

If you are our current customer your version of Traces API may differ from this reference as we continuously release new versions and tailor functionality for your individual needs. Follow your cluster URL or log in to the Knowledge Đ¡enter to see documentation customized to your version of the API, with your API keys and data.

Data migration has not finished yet!

Please refer to the Knowledge Center for the latest documentation.

TODO

Last updated