Skip to main content
POST
Generate WTN

Generate WTN

Generates a fully structured, compliance-checked digital Waste Transfer Note. This is a composite endpoint that runs carrier verification and waste classification in parallel internally, then combines the results into a single WTN document. Each WTN is persisted with a unique reference and can be retrieved later via GET /v1/wtn/.
Requires authentication via Authorization header. See Authentication.

Request

Method: POST Path: /v1/generate-wtn

Headers

string
required
Bearer token with your API key, e.g. Bearer wc_live_your_key
string
required
Must be application/json

Body Parameters

object
required
The business producing the waste
string
required
Business name
string
required
Business address
string
SIC code for the producer’s industry
string
Contact person’s name
object
required
The waste carrier
string
required
CBDU/CBDL registration number
boolean
Verify against EA register (default: true)
object
required
Details of the waste being transferred
string
required
Plain-English waste description
boolean
Classify into EWC codes (default: true)
string
Provide directly if auto_classify is false
number
Weight in kilograms
string
Container type (e.g. skip, wheelie_bin, drum)
object
required
The receiving waste facility
string
required
Facility name
string
required
Facility address
string
Environmental permit number (e.g. EPR/AB1234CD)
string
required
Date of waste transfer (YYYY-MM-DD format)

Response

Success Response (201)

string
Unique WTN reference (e.g. WTN-2026-0325-A7X9). Use this to retrieve the WTN later.
object
Confirms whether each legal requirement for waste transfer is met
boolean
True only when all duty of care checks pass

Duty of Care Checklist

Performance Notes

Total latency is typically 2-3 seconds, driven by the classification step. If you provide an ewc_code directly and set auto_classify to false, latency drops to ~500ms. WTNs are not cached. Each request creates a new document. The internal calls to /v1/verify-carrier and /v1/classify-waste use their own caches, so repeated WTNs for the same carrier or waste type are faster.

Error Responses

Example