Bulk Delete Wastes by Filters

const options = {
  method: 'POST',
  headers: {
    'x-api-key': '<x-api-key>',
    'x-organization-id': '<x-organization-id>',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({filter_hash: '<string>'})
};

fetch('https://api.dcycle.io/v1/waste/bulk-delete-by-filters', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "success_count": 123,
  "success_ids": {},
  "failed_count": 123,
  "failed_ids": {},
  "message": "<string>"
}

POST

waste

bulk-delete-by-filters

Bulk Delete Wastes by Filters

const options = {
  method: 'POST',
  headers: {
    'x-api-key': '<x-api-key>',
    'x-organization-id': '<x-organization-id>',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({filter_hash: '<string>'})
};

fetch('https://api.dcycle.io/v1/waste/bulk-delete-by-filters', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "success_count": 123,
  "success_ids": {},
  "failed_count": 123,
  "failed_ids": {},
  "message": "<string>"
}

Bulk Delete Wastes by Filters

Delete all waste records that match a set of filter criteria. This endpoint uses a two-step workflow: first fetch the waste list with filters applied (which returns a filter_hash), then call this endpoint with that hash to confirm you are deleting exactly what you saw.

Permanent Action: Deleting waste records is permanent and cannot be undone. All associated emissions data will be removed from your organization’s totals.

How It Works

Call GET /v1/wastes with your desired filters — the response includes a filter_hash field.
Call this endpoint with the same query filters and pass the filter_hash in the request body.
The API verifies the hash matches the current filter results to prevent stale-data race conditions.

Request

Headers

x-api-key

string

required

Your API key for authenticationExample: sk_live_1234567890abcdef

x-organization-id

string

required

Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Body Parameters

filter_hash

string

required

The hash returned in the filter_hash field of the waste list response. Confirms you are deleting exactly the records you saw.Example: "a3f1c2e4b5d6a7b8"

Query Parameters

facility_id is required. At least one additional filter parameter is required.

facility_id

string

required

The UUID of the facility to scope the deletion toExample: 660e8400-e29b-41d4-a716-446655440000

status[]

array[string]

Filter by record statusAvailable values: active, uploaded, success, loading, pending, in_progress, review, in_review, errorExample: status[]=error&status[]=loading

start_date

string

Filter records with a start date on or after this date (YYYY-MM-DD)Example: 2024-01-01

end_date

string

Filter records with an end date on or before this date (YYYY-MM-DD)Example: 2024-12-31

file_id[]

array[string]

Filter by source file UUIDs (e.g. to delete all records imported from a specific file)

created_at_from

string

Filter records created on or after this datetime (ISO 8601)Example: 2024-01-01T00:00:00Z

created_at_to

string

Filter records created on or before this datetime (ISO 8601)Example: 2024-12-31T23:59:59Z

co2e_status

string

Filter by CO2e calculation statusAvailable values: calculated, not_calculatedExample: co2e_status=not_calculated

identification_name[]

array[string]

Filter by waste identification names or invoice numbers

ler_code[]

array[string]

Filter by LER (European Waste List) codes

rd_code[]

array[string]

Filter by RD (recovery/disposal) codes

Response

Returns 200 OK with a JSON summary of the operation.

success_count

integer

Number of waste records successfully deleted

success_ids

array[string]

UUIDs of successfully deleted waste records

failed_count

integer

Number of records that failed to delete

failed_ids

array[string]

UUIDs of records that failed to delete

message

string

Human-readable summary of the operation

Example

# Step 1: get list with filters to obtain filter_hash
curl -X GET "https://api.dcycle.io/v1/wastes?facility_id=660e8400-e29b-41d4-a716-446655440000&status[]=error" \
  -H "x-api-key: ${DCYCLE_API_KEY}" \
  -H "x-organization-id: ${DCYCLE_ORG_ID}"

# Step 2: bulk delete using the filter_hash from the list response
curl -X POST "https://api.dcycle.io/v1/waste/bulk-delete-by-filters?facility_id=660e8400-e29b-41d4-a716-446655440000&status[]=error" \
  -H "x-api-key: ${DCYCLE_API_KEY}" \
  -H "x-organization-id: ${DCYCLE_ORG_ID}" \
  -H "Content-Type: application/json" \
  -d '{"filter_hash": "a3f1c2e4b5d6a7b8"}'

Successful Response

{
  "success_count": 12,
  "success_ids": [
    "550e8400-e29b-41d4-a716-446655440000",
    "660e8400-e29b-41d4-a716-446655440001"
  ],
  "failed_count": 0,
  "failed_ids": [],
  "message": "Successfully deleted 12 wastes"
}

Common Errors

401 Unauthorized

Cause: Missing or invalid API key

{
  "detail": "Invalid API key",
  "code": "INVALID_API_KEY"
}

409 Conflict — Filter Hash Mismatch

Cause: The filter_hash does not match the current filter results. The underlying data changed between the list call and the delete call.

{
  "detail": "Filter hash mismatch. The filters have changed since the list was loaded. Please refresh and try again."
}

Solution: Re-fetch the waste list with the same filters to get a fresh filter_hash, then retry.

422 Unprocessable Entity — No Filters Provided

Cause: Only facility_id was provided. At least one additional filter is required to prevent accidental mass deletion.

{
  "detail": "At least one filter parameter is required for bulk delete by filters."
}

422 Validation Error

Cause: Invalid query parameter value

{
  "detail": [
    {
      "loc": ["query", "status[]"],
      "msg": "value is not a valid enumeration member",
      "type": "type_error.enum"
    }
  ]
}

List Wastes

Retrieve waste records and obtain the filter_hash