What the DEFRA DWTS API is and why you need it

The Digital Waste Tracking Service API is the technical interface that allows software to submit Waste Transfer Notes directly to DEFRA's central database. You do not need to understand the API to use it. You do need to obtain the credentials that authorise your organisation to submit data through it.

Think of the API key as your digital signature. It tells the DWTS that the WTN submission came from your site, your permit number, your organisation. Without that key, your compliance software cannot submit anything.

Getting the key involves a registration process with DEFRA that verifies your identity, links your organisation to your environmental permit, and issues the credentials. The process is not instant. Expect it to take one to two weeks from start to finish.

Prerequisites: what you need before you start

A current environmental permit or waste management licence for each site that will be submitting WTNs. The permit must be in the name of the organisation that will hold the DWTS account. If your permit is lapsed, under renewal, or registered to a previous company name, sort that out before you start the DWTS registration. Permit amendments go through the Environment Agency and they are not fast.

A registered company with a valid Companies House number if you operate as a limited company. Sole traders and partnerships can register, but the verification process asks for different documentation. Contact DEFRA directly if you are unsure which category applies.

An email address that you check regularly. DEFRA sends confirmation emails, verification codes, and your API credentials to this address. Using a shared mailbox rather than an individual's email address avoids problems when someone leaves the company.

Step-by-step registration walkthrough

Step one. Go to the DEFRA Digital Waste Tracking Service portal. The URL for the public registration page is published on GOV.UK. You will be asked to create an account using your email address and a password. Use the shared mailbox approach.

Step two. Verify your email address. DEFRA sends a verification link. Click it within 24 hours. If you miss the window, you need to restart the account creation.

Step three. Link your organisation. You will be asked for your organisation name, Companies House number (if applicable), and your environmental permit number. The system cross-references the permit number against the Environment Agency's public register. If the names do not match, the registration stalls. This is the step that causes the most delays. Check the exact legal name on your permit before you type anything.

Step four. Identity verification. DEFRA requires proof that the person registering is authorised to act on behalf of the organisation. This may involve providing a scanned copy of a director ID, a letter of authority on company letterhead, or answering security questions based on the permit application.

Step five. Select the DWTS service. Once your organisation is verified, you need to explicitly request access to the DWTS API. This is not automatic. Look for the option labelled "API access" or "Developer credentials" in the dashboard. Select "Production API Code" unless you specifically want sandbox-only access.

Step six. Wait for approval. DEFRA reviews each API access request manually. The stated turnaround time is five to ten working days. During busy periods, it can take longer. You will receive an email with your API credentials when approved.

The Production API Code is a long alphanumeric string. Store it somewhere secure. If you lose it, you need to go through the request process again. There is no password reset for an API key.

Connecting your compliance software to the API

Once you have your Production API Code, you enter it into your compliance platform. In LoadLog, this is a single field in the organisation settings page labelled "DEFRA API Key." Paste the code, save, and the platform handles the rest. The API connection is tested automatically. If the credentials are valid, you see a green confirmation. If not, you see an error message that tells you what to check.

Most connection failures come down to three things. The API key was copied with a trailing space. The organisation details in the platform do not exactly match what DEFRA has on file. Or the key is a sandbox key and you are trying to use it against the production endpoint.

Testing with the sandbox environment

DEFRA provides a sandbox environment for testing. It is a complete mirror of the production system, but the WTNs submitted to it are not legal records. Use the sandbox to run through your workflow, train staff, and confirm that your data passes validation before you submit anything live.

LoadLog includes a sandbox mode toggle at the organisation level. Flip it to sandbox, run test submissions, check the results, and then switch to production when you are confident. The sandbox uses a separate API endpoint and separate credentials. You request sandbox access the same way you request production access, except you select "Sandbox API Code" instead of "Production."

A common mistake is testing in the sandbox and then forgetting to switch to production before the mandate date. Set a calendar reminder for the week before October 2026 to verify your production credentials are active and your first live submission has gone through.

If something goes wrong during registration

DEFRA's support team handles DWTS registration queries. Contact them through the portal rather than through the general Environment Agency helpline. The DWTS team has access to the registration system and can see where your application is stuck. The general helpline cannot.

Common problems include permit details not matching Companies House records, the verification email landing in spam, and the API access option not appearing because the organisation verification step has not been completed. Most of these are fixable by checking each step in sequence rather than assuming the system has made an error.

If your permit is still being processed by the Environment Agency, you cannot complete the DWTS registration until the permit is granted. You can prepare everything else, but the permit number is the lynchpin.

What happens after you have your key

Enter the key into LoadLog. Switch to sandbox mode. Run five or six test submissions across different waste types and carriers. Check that each submission returns an acceptance confirmation from the DWTS endpoint. Switch to production mode. Submit one live test WTN with a trusted carrier. Verify it appears in your DWTS dashboard.

Then you are ready. The key is active. The connection works. The data validation passes. Your site is technically compliant before the October deadline.

LoadLog connects to the DWTS API automatically once you provide your credentials. No manual integration, no middleware, no developer required.

How to Get a DEFRA DWTS API Key: Step-by-Step Guide