In Beta Phase
This feature is in the Beta phase. If you have any questions, ideas or suggestions please reach out to us at firstname.lastname@example.org.
The Delete Tracker API will delete the Tracker entity against the
Currently, the Tracker entities can be consumed in the Async APIs only. Support for the other APIs will be added soon.
|No||DEPRECATED. The JWT token you get from our authentication process.|
The following request parameter (query-param) is accepted in the URI:
trackerId - The unique ID of the Tracker to be deleted.
|The id of the Tracker that was deleted.|
|The type of the Entity. This will be set to |
|The status of deletion for this Tracker entity.|
In case of unsuccessful responses, the following error codes will be returned from the API:
|The 400 response code specifies that the request body or the parameters have incorrect key names or their values have types that are different than the ones expected.||Please read the message returned in the response to fix this error.|
|The 404 response code specifies that the Tracker with that specific ||Check the |
|The 500 response code specifies that the server failed to handle the request.||Please reach out to email@example.com if it persists even after multiple attempts.|
|The 502 response code specifies that the server failed to acknowledge the request. This may happen due to multiple reasons.||Please reach out to firstname.lastname@example.org if it persists even after multiple attempts.|
|The 504 response code specifies that the server failed to respond within the timeout duration.||Please reach out to email@example.com if it persists even after multiple attempts.|