Request to retry failed crashes

This service can be used to initiate a retry for sending crash data for all crashes that did not successfully reach your service.

As mentioned in the push crash data section, if your service is down or fails to accept crash data, the system will automatically retry pushing the data for 30 min after the accident, then once a day the following day. However, we understand that you may need the data sooner. In such cases, we recommend using this service.

This operation is asynchronous. The response contains the number of crashes that will be sent again, along with a unique task identifier, which can be used to monitor the progress of the retry.

If a task is already in progress, the service will return an error.

If you have your enterprise API key, you can try the API via this link.

Request the retry of failed crashes

post

Header parameters

x-dq-enterprise-api-keystringRequired

Enterprise API key

Responses

200

OK

application/json

401

Unauthorized

404

Not Found

application/json

409

Conflict

application/json

500

Internal server error

application/json

post

HTTPcURLJavaScriptPython

POST /v1/enterprise/push/crashes/failed/retry HTTP/1.1
Host: service.drivequant.com
x-dq-enterprise-api-key: text
Accept: */*

{
  "taskId": "6753030831fe9826412bac5c",
  "nbItems": 123
}

Response

The table below summarizes the response parameters.

Name	Type	Description
taskId	string	Unique identifier of the created task
nbItems	integer	Number of crashes that will be sent again (previously in a FAILED state)