{
  "id": "p__tz88luCbEWlcXtu",
  "site": "stories",
  "url": "https://yarnhen.com/p/p__tz88luCbEWlcXtu",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You run the integration that pulls waste collection data into your company's reporting system. Every night at the same hour, your job syncs. This morning a customer success manager asks you for the photo behind a contamination flag on one of your customer's bins, because the customer wants proof. You open the record and click the image link you saved. It doesn't load.\n\nThe AMCS Group AllContaminationEvent API is where this happens, and the APIs.io post about it is short on drama and long on one detail. The API is one operation wide: GET /visionai/api/integrator/allContaminationEvents/changes returns the contamination events AMCS's Vision AI has recorded on collection trucks. Each event carries a field called ImageSas, which the contract describes as \"the image SAS url of the Contamination Event.\" The contract also says it \"expires within 24 hours.\" The post puts it plainly: if you sync this feed once a day and store the URL, you will be storing broken links.\n\nSo what did you actually get each night? A lot, as it turns out. The operation's description lists the fields in a table, and they cover a whole truck lift. You get who: TenantId, CustomerName, CustomerSiteId, SiteName, CustomerType and CustomerAddress. You get where and when: VehicleId, Latitude, Longitude and Timestamp. You get the lift itself: GrossWeight, TareWeight, NetWeight, Lifter, ContainerId, RFID and WeighErrorCode. You get the verdict: ContaminationScore, WasteType, Materials and TotalSurfaceAreaVolume. And you get the evidence: ImageSas, QRCodeRawText and ExternalEventId.\n\nPaging works with bookmarks rather than page numbers. You pass since, which is the earlier extra.until, along with cursor, and you follow link.next until extra.until appears. That value is your bookmark for the next sync. The post notes that this design suits a polling integrator, and that a missed sync can only lose the images, because the event data stays retrievable from the bookmark. For you, that means the weights and scores are still there. Only the photo is gone.\n\nBefore you rebuild anything, you check which endpoint you are using. 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 post points out that the contract does not say this anywhere outside that one sentence.\n\nYou also notice the contracts disagree in places. 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. If you feed the spec to a code generator, it will find a reference to a scheme the contract never declares.\n\nHere the post turns to its own house. APIs.io says some of this is its to fix. The API page lists a baseURL of https://rstapi-sbx-svc-core.amcsplatform.com/erp/api/integrator/erp, which is 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 the catalog page is misleading. If you copied it from there, that would be one more reason things looked off.\n\nThe catalog also admits a bigger-picture wrinkle. AMCS Group is the largest publisher in its Waste Management industry, credited with 257 APIs and a Kin Score of 46.2, rated 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. But the AMCS directory also holds near-duplicate contracts, such as access-group alongside accessgroup and account-balance alongside accountbalance. That inflates the 257.\n\nSo you change your job. You treat the contamination image as perishable. On the sync that delivers the event, you download the photo and store your own copy, and you keep that instead of the link. You check whether your tenant uses the review process, so you call the right endpoint. And because the contract leaves the authentication model out, you ask AMCS how it actually works rather than guessing from cookieAuth.\n\nThe customer still wants last night's photo, and that one may be lost. But the next one won't be.\n\nRead the original: https://apis.io/2026/11/15/amcs-contamination-events-hand-over-a-photo-link-that-expires-in-24-hours/",
  "title": "The Contamination Photo You Stored Last Night Is Already Gone",
  "topics": [
    "waste-management",
    "api-integration",
    "computer-vision",
    "openapi"
  ],
  "published_at": "2026-11-15T21:40:01.687Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}
