{"repo":"psenger/Best-Practices-For-Rest-API","free":true,"listed":false,"github":"https://github.com/psenger/Best-Practices-For-Rest-API","clone":"git clone https://github.com/psenger/Best-Practices-For-Rest-API.git","description":"Pragmatic best practices for designing REST APIs — security, resilience, GraphQL, WebSockets, SSE, and more. 20 years of real-world experience.","language":null,"stars":31,"topics":["rest-api","api-design","api-gateway","api-security","best-practices","developer-guide","documentation","graphql","jwt","oauth"],"license":null,"category":"api-integrations-sdks","readme_excerpt":"Best Practices for Building REST APIs Written by Philip A Senger LinkedIn GitHub I've been building APIs for Service Oriented Applications for two decades. Many API design opinions and guidelines I have found are either academic in nature or less real world or practical. My goal with this document is to describe my version of best practices for a pragmatic API approach based on my experience and as a framework for my thoughts. I've found the following items to be the key to the success of my systems: The Human Aspect, Security and Permissions, and Implementation. [!TIP] Want an AI-powered review of your API design? This knowledge base powers the review-api-design skill — a Skill 2.0 compatible with any LLM that supports the Skill 2.0 standard. Install it and get structured, severity-tagged API design reviews drawn from the 110+ standards, RFCs, and guidelines curated here. Eval results — skill vs raw Claude: Scenario With Skill Raw Claude Delta ---------- ----------- ------------ ------- Minimal CRUD Endpoints 100% 50% +50% OpenAPI Spec (Payments) 100% 62% +38% Vague Verbal Description 82% 36% +46% Overall 94% 50% +44% The skill catches what raw Claude misses: sequential ID enumeration, BOLA risks, missing health endpoints, rate limiting gaps, RFC-specific citations, and more — all while staying at the design level instead of drifting into implementation. Install it now: Table of Contents 1. The Human Aspect - Adoption, Ease of Use, Documentation, Stability, Assurance - Intui","default_branch":null,"files":null,"tree":[],"storefront":"/r/psenger","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/psenger/Best-Practices-For-Rest-API/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}