Samdock Microservices HTTPS request support is limited to a subset of RFC 2616.
Always Check Header
Never access the response body without confirming over the HTTP Response Header first.
|Yes||Used for retrieving a collection or single resource|
e.g. Read Organizations, Read Persons.
|Yes||Used to create a new record.|
e.g. Add Person , Add Organizations.
|Yes||Used to delete a specified record|
e.g. Delete Persons, Delete Organization by ID.
|Yes||Used to update any existing record.|
e.g. Edit Person by ID, Add Last Seen Status
|Yes||Used to replace an entire resource rather than just updating a single field as done in |
e.g. Change Tenant Logo by ID
Some of the Samdock Microservices has a tendency to create new entities if the passed id does not exist within our system. Here is the list of endpoints that has entity creation implemented over PATCH methods.
Samdock Microservices documentation does not include every possible result for each microservice. It is advised to view individual microservice for specific results associated with a given endpoint and assume there is a wide range of possible responses available for operations. This includes authorization failures, format issues, or platform-related operational issues.
Request successes are returned with HTTP status codes starting with
2xx. Below is a partial list of responses.
|Success||The request was successful.|
Request errors are returned with HTTP status codes starting with
4xx and server errors are starting with
Checking Error Codes
The developer shall ensure to handle appropriate application flows as per the Error Response Codes.
Same HTTP error codes are expected based on similar errors as depicted in the below list.
|Failure||Unauthorized error or Token expired. User need to generated token.|
|Server Error||Server processor error. The user is advised to contact the Samdock Support.|
Additional HTTP Result Codes
Other standard HTTP errors may be generated by our stack and not directly from our API. Here are the categories of possible Standard HTTP response codes.
1xx: Communication transfer protocol-level information.
2xx: This indicates that the client's request was accepted successfully.
3xx: Indicates that the client must take some additional action to complete their request.
4xx: This category of error status codes points to the clients.
5xx: This category of error is related to server exceptions due to an internal incapability to perform the request. The user is advised to contact the Samdock Support.
For more information please refer https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
Updated about 2 years ago