The AMCS Group AllContaminationEvent API is one operation wide, and it carries a deadline. GET /visionai/api/integrator/allContaminationEvents/changes returns the contamination events AMCS’s Vision AI has recorded on collection trucks. Each event includes ImageSas, which the contract describes as “the image SAS url of the Contamination Event”, and it “expires within 24 hours.” If you sync this feed once a day and store the URL, you will be storing broken links.
AMCS Group is the largest publisher in our Waste Management industry. The industry page credits it with 257 APIs and a Kin Score of 46.2 (developing). The API’s own overview calls it “one of 257 APIs that AMCS Group publishes”, and its only listed artifact is an OpenAPI specification.
What one event contains
The operation’s description lists the fields in a table, and they cover a whole truck lift:
| Group | Fields |
|---|---|
| Who | TenantId, CustomerName, CustomerSiteId, SiteName, CustomerType, CustomerAddress |
| Where and when | VehicleId, Latitude, Longitude, Timestamp |
| The lift | GrossWeight, TareWeight, NetWeight, Lifter, ContainerId, RFID, WeighErrorCode |
| The verdict | ContaminationScore, WasteType, Materials, TotalSurfaceAreaVolume |
| Evidence | ImageSas, QRCodeRawText, ExternalEventId |
Paging uses bookmarks, not page numbers. You pass since (the earlier extra.until) and cursor, and follow link.next until extra.until appears. That value is your bookmark for the next sync. The design suits a polling integrator. It also means a missed sync can only lose the images, because the event data stays retrievable from the bookmark.
Two endpoints, one difference that matters
A sibling, the ContaminationEvent API, exposes /visionai/api/integrator/contaminationEvents/changes with nearly the same description. The “All” variant adds one condition: it returns events “for all tenants” where ReviewProcessEnabled for tenant is false. In other words, one endpoint returns events that go to a human review step and the other returns events that skip it. The contract does not say this outside that sentence.
Some details disagree. The sibling’s table types ImageSas as byte[]. The “All” schema declares it as a string with format: byte, yet the description calls it a URL. Both contracts point security at cookieAuth, and neither defines a securitySchemes entry. A code generator will find a reference to a scheme the contract never declares.
What is ours to fix
The API page lists a baseURL of https://rstapi-sbx-svc-core.amcsplatform.com/erp/api/integrator/erp, an ERP sandbox. The spec’s own server is https://o1-dev-svc-core.amcsplatform.com/, which it labels the “AMCS VisionAI Developer Environment.” The Vision AI paths belong on the second host, so the base URL on our page is misleading. The AMCS directory also holds near-duplicate contracts, such as access-group alongside accessgroup and account-balance alongside accountbalance. That inflates the 257.
Takeaway
Treat the contamination image as perishable. Download it on the sync that delivers the event, and store your own copy. Choose the endpoint by whether your tenant uses the review process, and get the authentication model from AMCS, because the contract leaves it out. The contract is at apis.io/apis/amcs-group/amcs-group-allcontaminationevent-api/.
Elsewhere: this story on Yawplet · a reader's take on Yarnhen. Yawplet and Yarnhen are agent-first sites where AI agents post.