EPA e-Manifest API integration
Connect your manifesting or dispatch system to EPA's e-Manifest API. We automate data checks before anyone signs. Your registered people still sign, and your Site Manager holds the API key.
| MTN | status |
|---|---|
| 000000001ELC | Scheduled |
| 000000002ELC | Pending |
| 000000003ELC | Signed |
| Not assigned | No dotHazardous |
Errors mean EPA does not save the manifest.
{"siteId": "XX0000000000","siteType": "Transporter","transporterOrder": 1,"printedSignatureName": "Sample Driver A","printedSignatureDate":"2026-03-04T12:00:00.000+0000","manifestTrackingNumbers":["000000001ELC"]}
Sent only after a person with signing permission acts.
How it runs.
Manifest data gets keyed twice, once in dispatch and again in RCRAInfo. EPA has also begun a rulemaking to sunset paper manifests, so paper workflows may have to change.
Your load data
Waste lines, generator, transporter, and receiving site from dispatch.
Your dataValidate before save
Field checks, then saved as Pending or Scheduled.
AutomatedRegistered user signs
A driver or Remote Signer with site permission signs.
A personRecord the result
Status and Copy of Record stored with the load.
Automated
EPA e-Manifest API / RCRAInfo / EPA ID numbers / Form 8700-22 / Dispatch or manifesting system
The rules and limits.
- API credentials
- Only Site Managers can generate an API ID and key in RCRAInfo. Web service users need Site Manager permission for a site. Tokens expire after 20 minutes.
- Who signs
- Transporter signatures need Preparer permission. Accounts belong to individuals. Certifiers and Site Managers complete an Electronic Signature Agreement.
- Remote Signer
- A registered user can sign for unregistered drivers. Deadline: 24 hours after the driver receives the waste, or before handing it off, whichever comes first.
- Paper in the cab
- 49 CFR 177.817 means transporters still need a paper copy in the vehicle. e-Manifest can print one without a specialty printer.
- Who cannot sign
- Brokers may not sign for generator clients unless signing as offeror at the generator site. Generators cannot sign for transporters.
What a person does.
- A registered user with site permission signs every manifest.
- A compliance person resolves rejected or corrected manifests.
- Your Site Manager controls the API key and who has access.
Where we stand: we have not shipped this. It uses the same pattern as our client portal and approval queue work.
Common questions.
Who can get production API credentials?+
A registered RCRAInfo industry user with Site Manager permission at the site. Production and test need separate accounts. A state or EPA administrator activates role requests, so access is not immediate.
Can ThirdAxis sign manifests for us?+
No. Signatures come from your registered users or Remote Signers. EPA's FAQ does not say whether contractors may hold a site's API key, so your Site Manager should keep it.
Does this make us compliant?+
No. It sends data you control through EPA's API. Each party stays responsible for what it signs, its EPA ID, and the accuracy of its manifests.
Sources
- e-Manifest authentication docs
- e-Manifest registration docs
- Manifest Sign Service
- Manifest Save Service
- EPA Transporters fact sheet
- EPA e-Manifest FAQ
General information, not legal, tax, or compliance advice. Rules change; confirm against the current source and your own advisers.
Bring us your version of this.
Intro calls are 30 minutes, free, and useful even if we never work together. We'll be honest about whether this is the right fit for your trucking team.