n8n’s guide to API versioning strategies for stable workflow integrations is written for the consumer, not the provider. It walks the four places a version can live (the URL path like /v1/products, an HTTP header, a date like /2026.10/, a query parameter) and is clear about the tradeoffs: a path version is visible in logs and caches cleanly, a header version keeps URLs stable but hides which version answered, and a query parameter can fool a cache that ignores it. The advice that matters is about the end of life: watch for a deprecation header, read the sunset header for the date, and when a provider returns 410 Gone, “Don’t retry the same version or send the same request.”
There are no vendor figures to discount. The product part of the post is that n8n’s HTTP Request node lets you pin the version in the URL, header or parameter rather than “relying on whatever version the provider uses by default,” and route a 410 or a deprecation warning into an Error Trigger workflow. That survives on its merits. Pinning a version is the single most useful habit an integrator can have, and treating sunset as a signal to act on, not a log line, is the right instinct.
The catalog lets us turn the advice around. n8n on apis.io carries 22 API pages for its own instance-scoped REST API, and the ones this story touches are the N8n Workflow API that holds the versioned HTTP Request node, the N8n Execution API behind the execution history the post uses to replay a failed run, and the n8n Source Control API, which is how teams version the workflows themselves. The agentic access profile counts 73 operations, 50 of them acting.
Here is the tension. n8n scores 67.0 on the Kin Score, exemplar, with access clarity at a perfect 100.0 and developer ergonomics at 85.7. Contract governance, the facet that measures versioning, change history and deprecation signalling on n8n’s own contract, is 4.5. Agent Readiness is 33.1, with error semantics, OpenAPI examples, dry-run mode and agent skills lit, and idempotency and reversibility unlit. n8n has written one of the clearer explanations of how a consumer should read deprecation and sunset signals. Its own API gives the catalog almost nothing of that kind to read.