Tag: api-design

Found 447 results for 'api-design'.

1) design - How to handle or design review system with pagination?
2) api-design - Why do so many standards for JSON API response formats contain a "success" property in the response body instead of just using HTTP status codes?
3) api-design - Should I return an HTTP 400 (Bad Request) status if a parameter is syntactically correct, but violates a business rule?
4) api-design - Message validation in async messaging-based services
5) rest - Should a REST API always document its response content?
6) api-design - Should a REST API return a 500 Internal Server Error to indicate that a query references an object that does not exist?
7) design - How to Properly Design an API Prefetch System
8) design - Designing an API with access tokens, how to handle GET requests?
9) rest - Is it an anti-pattern for a REST-ful API object to contain different fields depending on context?
10) rest - Which REST API URI should be used for querying a relation to a single model object?
11) rest - Microservices based API, how to handle long lists requests
12) rest - REST API Oauth 2 - Which grant type to use?
13) c# - Does it make sense to qualify an error as an HTTP error without an HTTP client-server communication
14) rest - What http codes should i return when user request file which doesn't meet his requirements
15) rest - What is the best pattern for adding an existing item to a collection in REST API?
16) rest - Resource representations and REST API documentation tools
17) rest - REST API with files as resources?
18) rest - REST API endpoint returning detailed or summary data
19) rest - GET resource state with JSON body or HTTP code
20) rest - What is a proper response status code to POST when parent resource is not found?
21) api - How to handle business rules with a REST API?
22) c# - Multiple HttpClients in .NET Core Console Application
23) design-patterns - mongodb queries architecture - resolving lots of nested referenced objects
24) database-design - Suggested method for "simplifying" EAV
25) mvc - Should you write your back-end as an API?
26) design-patterns - How to architect user authentication from client applications?
27) rest - How to design API endpoints for post a child object and for getting all the children of all the parents?
28) rest - RESTful API and i18n: how to design the response?
29) api - Design for a API server with 3rd party OAuth flow
30) rest - Should a GET endpoint in API server A make a POST request to a separate API server B?
31) design-patterns - Best practices for sending various details about REST resource in a reply from service
32) design - Specialized API endpoints or multiple calls to generic resources?
33) api - How to transmit credentials in API
34) design - REST API - Should API Return Nested JSON Objects?
35) design - Should a web app for a service access its data via its own API or directly?
36) rest - Manipulate database data through Single REST API request or Multiple consequent requests?
37) api - Should I add a key to the items of my REST API response?
38) rest - How to correctly implement key=value storage REST API
39) web-development - How to safely chain several API requests for a single user
40) api - Should an http API client hide the http response object?
41) security - Restful User/Password Authentication
42) rest - Should I return user data in an authentication endpoint using JWT?
43) php - Strategy for Public / Private API, Encrypted (or Hashed) Data, and Server Compromise
44) rest - API design dilemma: to REST or not to REST
45) rest - REST: How to "upsert" a resource without an specific resource URL
46) design - RESTful way to handle related resource for both specific instances of a resource and all of that resource
47) design-patterns - How to handle state of an object? And how to enrich the state transition logic?
48) rest - Good practice for status code returned by restful API when validating a token
49) rest - Rest application header based vs path based service routing
50) rest - Should I be permissive of unknown parameters?