Methodology:REST API Pattern: Difference between revisions
From Devguid
No edit summary |
No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
This is a pattern for how to construct a REST API according to us. | This is a pattern for how to construct a REST API according to us. | ||
== StatusCodes == | |||
400 - client errors | |||
500 - server errors | |||
| Line 8: | Line 12: | ||
https://devblogs.microsoft.com/dotnet/introducing-the-reliable-web-app-pattern/ | https://devblogs.microsoft.com/dotnet/introducing-the-reliable-web-app-pattern/ | ||
https://github.com/michidk/TwitchCSharp | |||
https://github.com/JohnnyCrazy/SpotifyAPI-NET/blob/master/SpotifyAPI.Web/Models/Request/RequestParams.cs | |||
https://github.com/OAI/OpenAPI-Specification | |||
https://learn.microsoft.com/en-us/azure/architecture/best-practices/api-design | |||
[[Category:REST API]] | [[Category:REST API]] | ||
Latest revision as of 10:25, 8 May 2023
About
This is a pattern for how to construct a REST API according to us.
StatusCodes
400 - client errors 500 - server errors
References
https://devblogs.microsoft.com/dotnet/introducing-the-reliable-web-app-pattern/
https://github.com/michidk/TwitchCSharp
https://github.com/OAI/OpenAPI-Specification
https://learn.microsoft.com/en-us/azure/architecture/best-practices/api-design
