---
title: Discover our Refcard RESTful API Design
description: Designing a REST API raises questions and issues for which there is no universal answer, which is what makes this job fascinating.
image: https://publication.octo.com/hubfs/OCTO%20Publications/Refcards/RESTful%20API%20Design/Refcard_API_CLOSE%20(1).png
---
[Fr](https://publication.octo.com/fr/telechargement-refcard-restful-api-design) [En](https://publication.octo.com/en/download-refcard-restful-api-design)
# RefCard RESTful API Design
[Download RefCard](https://publication.octo.com/en/download-refcard-restful-api-design#ancre)
## Description.
As soon as we start working on an API, design issues arise. **A robust and strong design is a key factor for API success**. A poorly designed API will indeed lead to misuse or – even worse – no use at all by its intended clients: application developers. **To facilitate and accelerate the design and development of your APIs**, we share our vision and beliefs with you in this Reference Card. They come from our direct experience on API projects.
Designing a REST API raises questions and issues for which there is no universal answer. **REST best practices are still being debated and consolidated**, which is what makes this job fascinating. “Purists” insist upon following REST principles without compromise. “Pragmatics” prefer a more practical approach, to provide their clients with a **more usable API**. The proper solution often lies in between.
.png)
### On the menu
- RESTful API principles as described in the literature (Roy Fielding, Leonard Richardson, Martin Fowler, HTTP specification...)
- The API practices of the Web Giants
## REST best practices are still being debated and consolidated, which is what makes this job fascinating.
## Download Refcard (PDF)
-
-
-
-
Version 3.0.121 (Build officiel)