82% of orgs are API-first. Collaboration and velocity depend on it. Read the report

Breaking Changes logo. Illustration.

Weekly talk show on APIs

An Overview of the Idempotency Request Header Field

Listen, watch, or subscribe

Breaking Changes is a weekly talk show where guests discuss, debate, and solve the latest topics around APIs.

Listen on Apple PodcastListen on YouTubeListen on Spotify PodcastListen on Amazon Music

Postman Chief Evangelist Kin Lane welcomes Jayadeba Jena and Sanjay Dalal to discuss their recent submission of a draft to the IETF Network Working Group for an Idempotency-Key HTTP header field.

Speakers

Kin Lane

Kin Lane

Chief Evangelist

Postman

Jayadeba Jena

Jayadeba Jena

Director, API Platform

PayPal

 Sanjay Dalal

Sanjay Dalal

API Digital Transformation Leader

Colligso

About

The HTTP Idempotency request header field can be used to carry idempotency key in order to make non-idempotent HTTP methods such as POST or PATCH fault-tolerant.

In this Breaking Changes tl;dr mini-episode, Postman Chief Evangelist Kin Lane welcomes Sanjay Dalal and Jayadeba Jena to discuss their recent submission of a draft to the IETF Network Working Group for an Idempotency-Key HTTP header field. The discussion aims to get insights into standardization within the API sector and understand the value of establishing standards from existing patterns.

Broken collaboration leads to broken APIs.

Ninety-three percent of API teams still face collaboration blockers. The 2025 State of the API report reveals how you can unlock the productivity gains that API-first promises, but scattered tooling prevents.

Read the report
API Platform Illustration