Robert Lasch

Robert started EndPointBlank after running into the same problem again and again over many years of software development: nobody knew which services were calling an API, or which version of it they were on. Changing an API was very risky, because of the number of clients hitting the existing one.

Robert is the author of the EndPointBlank guides: how to retire an API version, how to tell the clients still calling it, and how to change credentials without an outage. They are for the people who own an API other teams or companies depend on.

Robert Lasch on LinkedIn

More about the company behind the product is on the about page.

• API versioning strategies: URL path, header or query parameter?

  October 30, 2026

  How the common API versioning schemes compare, which to pick for a public API, when a change deserves a new version, and how to plan retiring the old one.

• Deprecation and Sunset headers: a practical guide

  October 26, 2026

  The Deprecation (RFC 9745) and Sunset (RFC 8594) HTTP headers: exact syntax, common mistakes, and code for Rails, Express, Phoenix, FastAPI and Spring.

• An API deprecation policy template

  October 26, 2026

  A copy-and-edit API deprecation policy: notice periods, how consumers are told, support for deprecated versions, extensions, and what happens after retirement.

• API deprecation email templates, from announcement to retirement

  October 26, 2026

  Five copy-and-edit emails for retiring an API version: the announcement, reminders 30, 7 and 1 day out, and the day after.

• How to rotate API secrets without downtime

  October 26, 2026

  Rotate API client secrets with an overlap window, so callers switch on their own schedule: the steps, server-side code, and the pitfalls.

• 410 Gone vs 404: what to return for a retired API endpoint

  October 26, 2026

  Why a retired API endpoint should return 410 Gone, not 404, what the response body should say, and code for Express and Phoenix.

• How to find which clients still call an old API version

  October 25, 2026

  Build a list of every client still calling your old API version, with call counts and last-seen times, before you retire it.

• How to deprecate an API version without breaking your customers

  October 22, 2026

  A step-by-step playbook for retiring an old API version: find who still calls it, announce it in the response, send reminders, and retire on evidence.