Skip to main content
GET
List Waste Emission Factors
← Wastes API Returns a paginated list of all waste emission factor entries. Each entry maps a LER code (European Waste Catalogue) and an RD code (disposal/recovery operation) to a waste_efs_id.
Read-only. waste_efs_id is no longer accepted by POST /v1/wastes or PATCH /v1/wastes/{waste_id} — this endpoint now only serves existing records and reporting. To attach a standard emission factor on create/update, use waste_ler_code_id/waste_rd_code_id instead.
This is global reference data — it is the same for all organizations, and it only changes when Dcycle ships new factors, so it is safe to cache. Use the low_code and rd_code filters to narrow down to the entries relevant to your waste records.

Request

Headers

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Query Parameters

string
Filter by region code. Every factor Dcycle ships is global, so pass GLO unless support tells you otherwise — any other region code returns an empty list.Example: GLO
string
Filter by exact LER code (European Waste Catalogue). Six digits, no spaces, plus a trailing * for hazardous waste, which is part of the code. Some entries carry a source prefix instead (DEFRA_2024-020107, OCCC_2025-140601*); the filter is an exact match on the stored value, so pass the code exactly as the catalog returns it.Examples: 200101, 130507*, OCCC_2025-140601*
string
Filter by exact RD code (disposal/recovery operation). Zero-padded to two digits — R3 returns nothing, R03 does. The catalog runs D01–D15 and R01–R14, and entries with no treatment recorded come back with rd_code: null.Examples: D09, R03
integer
default:"1"
Page number for paginationExample: 1
integer
default:"50"
Number of items per page (max 100)Example: 50

Response

array[object]
Array of waste emission factor entries
integer
Total number of entries matching the current filters
integer
Current page number
integer
Number of items per page

Example

Successful Response

Common Errors

401 Unauthorized

Cause: Missing or invalid API key
Solution: Verify your API key is valid and active.

Create Waste

Create a waste record (use the kernel LER/RD codes, not waste_efs_id)

List Wastes

Retrieve existing waste records for a facility