Build one route inventory

List API hosts, versions, routes, authentication methods, owners and data types. Include mobile, partner, internal and test APIs. Check API gateways, source code and logs for routes that are not in the main documentation.

Mark each route as supported, deprecated or retired. Give every old version a named owner and a planned end date.

Check whether old routes still receive traffic

Review gateway and application logs for real use. Contact known partners before a removal. Do not rely on a version label alone; a route may remain accessible under a second hostname.

Check whether an old route has weaker authentication or missing fixes. Reduce exposure while you plan a safe migration.

Retire and verify

Publish a clear deprecation notice and migration path. Disable the route when the agreed period ends, then confirm that requests no longer reach the old code.

Update API documentation and asset records. Repeat the inventory after major product and infrastructure changes.