Delete Geofences in Bulk
DELETE/geofences
This endpoint deletes up to 1000 geofences in a single request, identified by their unique IDs. Each ID is reported independently, so IDs that cannot be deleted do not prevent the rest from being deleted. To delete a single geofence you may also use DELETE /geofences/{geofence_id}.
Request
Responses
- 200
- 400
- 401
- 403
- 422
- 429
- 500
- 503
Successful operation. This status is returned whenever the request itself was valid, including when no geofence could be deleted. Inspect the per-ID status to determine the outcome of each ID.
The request body is declared as JSON but cannot be parsed, or is not a JSON object or array. Nothing was processed.
Unauthorized access. Authentication is required.
Access is forbidden. The user does not have permission to access this resource, or the account is not currently active.
Validation failed for the input parameters.
Too Many Requests - the endpoint's rate limit has been exceeded. Retry after the number of seconds in the Retry-After header.
Response Headers
Seconds to wait before retrying. The same value as X-RateLimit-Retry-After-Seconds when that wait is non-negative. If the computed wait is negative, Retry-After is floored at 0.
Unix timestamp of the next earliest successful request.
Seconds until the next earliest successful request.
Internal server error.
Service temporarily unavailable. The request did not complete and can be retried after the number of seconds in the Retry-After header, when one is sent.
Response Headers
Seconds to wait before retrying. Sent with db_busy and db_pool_timeout.