Software Development

Stripe Inspired API Design Rules

JSON HTTP API design rules distilled from Stripe — resource modeling, identifier schemes, URL structure, request/response wire format, pagination, errors, idempotency, versioning, naming, webhooks, and authentication. Triggers on tasks involving OpenAPI specs, API design reviews, schema decisions, endpoint shaping, error envelope design, webhook delivery, or any "is this API well-designed" question. Apply when designing, reviewing, or refactoring a JSON HTTP API — even when the user doesn't mention Stripe by name, since the rules are general API-design principles distilled from the industry's most-copied reference.

Publisher / source

pproenca/dot-skills (found on skills.sh)

Upstream record

pproenca/dot-skills

Version

Version 3

Published

2026-11-02

Publication review

Approved for publication

Content fingerprint

ed9bb6363cf69145a24a8f86d08a917746df9cde6113eba18667e5230e6b3481