HTTP Response Codes
All MedsAPI Dynamed Decisions endpoints could return any one of the following response codes. JSON responses for a 200 will vary depending on the endpoint.
|Generic successful execution.
|Required property is missing or contains an illegal value.
|No authentication credentials were passed OR incorrect authentication was passed
|The request requires authentication and none was provided.
|The client is not authorized to access the resource, although it may have valid credentials
|The authentication credentials do not have access to this resource.
|List of types comes back empty (can only occur if there is a data problem)
|The server has not found anything matching the request URI. This either means that the URI is incorrect or the resource is not available.
|Method Not Allowed
|Using a POST, PUT or DELETE request
|The server has not implemented the requested HTTP method.
|content-type header was something other than json
|The server cannot return the content-type requested.
|Unsupported Media Type
|content-type header was a format that is not recognized by the server
|The server cannot understand the requested content-type.
|Error was thrown by the middle service
|The requested action cannot be performed and may require interaction with APIs or processes outside of the current request. This is distinct from a 500 response in that there are no systemic problems limiting the API from performing the request.
|Too Many Requests
|Rate limit was exceeded
|The server must return this status code if the rate limit for the user, the application, or the token has exceeded a predefined value.
|Internal Server Error
|Error was thrown by the edge service
|This is either a system or application error and generally indicates that although the client appeared to provide a correct request, something unexpected has gone wrong on the server.