Delete records in bulk

Removes many records in one request. There is no undo — page through GET /link first if you need a record of what is about to go.

Base URL: https://api.power301.com/v1
Auth: Bearer token
Idempotent: Yes
Returns: application/json

The request

Call DELETE /bulk with your bearer token. Narrow or order the result with the query parameters below.

# Delete records in bulk
curl -X DELETE "https://api.power301.com/v1/bulk?filter=value" \
  -H "Authorization: Bearer $POWER301_TOKEN"

Query parameters

Parameter	Description
sortoptionalstring	Sort results by field. Prefix with - for descending order. Available sorts: id, created_at, updated_at, total_clicksid-idcreated_at-created_atupdated_at-updated_attotal_clicks-total_clicks
filterRequiredobject	Records the operation applies to. Accepted as a query object (`filter[host]=go.example.com`) or as a `filter` object in the JSON body. At least one filter must carry a value, or every record of the workspace would match. Available filters: id, host, path, tld, handler, type, destination, search, tags, traffic, dns_correct, status, created_after, created_before
filter[id]optionalstring
filter[host]optionalstring
filter[path]optionalstring
filter[tld]optionalstring
filter[handler]optionalstring
filter[type]optionalstring
filter[destination]optionalstring
filter[search]optionalstring
filter[tags]optionalstring
filter[traffic]optionalstring
filter[dns_correct]optionalstring
filter[status]optionalstring
filter[created_after]optionalstring
filter[created_before]optionalstring

The response

A 200 returns the record as JSON.

{
  "affected": 1,
  "pending": 1
}

Status codes

200

SuccessRecords deleted (affected), and of those, how many are still being deleted in the background (pending). Up to a few seconds of deleting runs in the request, so most deletes come back with pending 0 and are already gone from listings and counts; a larger one returns as soon as that time is up and the rest leaves the listing within moments. Tags, history, monitors and the edge configuration are updated in the background either way.

401

UnauthenticatedUnauthenticated

422

Validation failedA field was rejected. errors lists every field with its reason.

429

Too many requestsToo many requests

484

Bad requestThe workspace role of the authenticated user is too low for this action.