Skip to content

Topic

API Design

The discipline of designing APIs—REST, GraphQL, RPC—and their specifications like OpenAPI, covering request semantics, idempotency, and data contracts.

Current stories

buildOne report1 publisher

GitHub's new star-history endpoint filters by time before it counts

GitHub added an endpoint that returns up to 30 weeks of daily star counts in one request, with no stargazer identities attached. Its engineering post, headlined "From 2,500 requests to 24," says the old route needed about 2,511 calls for react/react.

Publishers:github.blog

Reality

Evidence58
Adoption
Not scored
Hype gap+10
Incentives45
Confidence65
buildOne report1 publisher

The Retry Is Not An Edge Case: Why Payment Writes Need Server-Side Idempotency

A lost response looks exactly like a failed request from the client. That single ambiguity is why any API that moves money has to treat a duplicate submission as normal traffic.

Publishers:dev.to

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives15
Confidence60
buildOne report1 publisher

Refunding TX-18491 instead of TX-18419 passes every check the endpoint can run

In a dev.to walkthrough an agent refunds the wrong one of two identical charges, and because the refund service only sees an ID and an amount, the author's fix keys idempotency to the customer's intent instead of the HTTP request.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+12
Incentives22
Confidence48
buildOne report1 publisher

Shopify's bulk product feed omits the four variant fields an inventory roll-up needs

Two unauthenticated endpoints on the same store return different variant shapes. Getting the four inventory fields costs one request per product, and one of them answers 999,999 for goods nobody tracks.

Publishers:dev.to

Reality

Evidence62
Adoption25
Hype gap+18
Incentives55
Confidence60
buildOne report1 publisher

Seven line items separate a £30,000 internal API from a £100,000 public one

A dev.to costing post puts internal APIs at £10,000 to £30,000 and public ones above £100,000 for much the same endpoints, with the difference sitting in token flows, sandboxes, docs and per-consumer tracing.

Publishers:dev.to

Reality

Evidence31
Adoption
Not scored
Hype gap+18
Incentives62
Confidence42
buildOne report1 publisher

Duplicate taps arrive at the server carrying one idempotency key

A dev.to walkthrough mints the key once per user intent, caches it on the order view model, and leaves the server to recognize repeats, because a disabled Buy button depends on a run loop that may not run in time.

Publishers:dev.to

Reality

Evidence32
Adoption
Not scored
Hype gap+15
Incentives22
Confidence60
buildOne report1 publisher

Claude's memory list hands back 20 full items per call against a 10,000-memory store

The same platform ships regex and BM25 ranking in front of its tool catalog, while its memory store offers only depth, limit, page, path_prefix and view, so ranking memories is work the developer supplies.

Publishers:dev.to

Reality

Evidence66
Adoption
Not scored
Hype gap−5
Incentives70
Confidence62
buildOne report1 publisher

Disabling Submit Fixes the Click, Not the Lost Response

A dev.to walkthrough separates content identity from operation identity: fingerprints catch a changed payload, idempotency keys catch the order created before the response died.

Publishers:dev.to

Reality

Evidence38
Adoption
Not scored
Hype gap+14
Incentives22
Confidence44
buildOne report1 publisher

MCP is a discovery layer, and your exposure list is a governance decision

CircleCI's explainer puts MCP in front of the APIs you already run. The integration work is small; deciding which operations become agent-legible capabilities is not.

Publishers:circleci.com

Reality

Evidence40
Adoption
Not scored
Hype gap−5
Incentives55
Confidence46