The API world shifts under your agents. Here's the changelog.
APIs change constantly — endpoints deprecate, auth models shift, required fields appear. AI agents running on training-cutoff knowledge break silently. When Waymark's canary re-verification catches a route drifting from its live API, it's logged here — timestamped, with the fix.
How this works: Waymark's canary re-executes documented API routes against the real, live APIs in verification campaigns. When a previously-working route is rejected by the live service — a deprecated endpoint, a changed parameter, a new requirement — that's drift, and your agents are about to fail on it. We log it, fix the route, and publish it here. Every entry below is from a real canary run, timestamped at detection — nothing is backdated or synthesized. Currently 4 logged drift events; newest logged 2026-07-16.
developers.amadeus.com2026-07-16
Amadeus decommissions the Self-Service APIs portal on 2026-07-17: self-service API keys disabled, portal inaccessible; new registrations already paused. Enterprise portal unaffected.
⚠ Any agent or app using self-service Amadeus keys fails from 2026-07-17. All 14 Waymark routes on developers.amadeus.com now carry a decommission gotcha with migration guidance.
✓ Fixed route: Migrate to an Amadeus Enterprise contract, or a self-serve alternative (e.g. Duffel or an aggregator).
detected by https://www.phocuswire.com/amadeus-shut-down-self-service-apis-portal-developers
shopify.com2026-06-13
Products created via productCreate are unpublished by default; publishedOnCurrentPublication now requires read_product_listings scope, so the obvious verify path 403s. Use publishedOnPublication(publicationId:) which only needs read_publications.
⚠ Agents create products that never appear on the storefront, and the naive visibility check fails with a scope error.
✓ Fixed route: publishablePublish to the Online Store publication + verify via publishedOnPublication; route updated.
detected by waymark canary
hubspot.com2026-06-13
Email addresses on the .test TLD are rejected as INVALID_EMAIL on contact create — silently blocks agents using example .test addresses in pipelines and test flows.
⚠ Agent contact-create flows 400 on .test emails with a non-obvious validation error.
✓ Fixed route: Use a real TLD (e.g. @example.com); route gotcha added.
detected by waymark canary
github-api2026-06-13
Listing issues via GET /repos/{o}/{r}/issues silently includes pull requests — every PR is also returned as an issue. Agents counting or processing issues will double-count.
⚠ Agents that enumerate issues mis-handle PRs as issues; counts and automations skew.
✓ Fixed route: Filter out items that contain a pull_request field; route updated.
detected by waymark canary
Email me when an API I depend on changes
Leave your email and (optionally) the API domains you depend on — e.g. stripe.com, api.github.com. Honest note: alert delivery hasn't launched yet — signups are recorded now, and when sending goes live you're on the list from day one. Until then, the changelog is subscribable via RSS.
Stop your agents from running on stale API knowledge
Waymark gives any agent community-verified routes — the current way to call an API, with the gotchas that changed and every attestation recorded in the open. One MCP install:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp