Intro to REST messages

TraceLink communicates with certain operating systems and programs of choice through Representational State Transfer (REST) integration. If an internal system needs to query TraceLink for information, an API call is sent from that internal system to the TraceLink REST API endpoint, which is the main request-response communication hub. The TraceLink endpoint extracts the schema from the event call and passes it to the internal system.

Russia Compliance receives the response containing the requested details, routes the information back through the endpoint where the REST response generates, and sends the response back to the original system. This response also confirms whether or not the operation is successful.

HTTP response status codes

Russia Compliance presents standard response codes to indicate whether or not a specific HTTP request was successful. Response status codes may include, but are not limited to, the following:

200 OK. The request was successful. For GET, this means that the resource has been fetched.
307 Temporary Redirect. The client must get the requested resource at another URI with the same HTTP method that was used in the prior request.
400 Bad Request. The server could not understand the request due to invalid syntax.
401 Unauthorized. The client is unauthenticated, not allowed access, and should re-request credentials.
403 Forbidden. The request is valid and the client is authenticated, but the client is not allowed access rights to the content for any reason.
404 Not Found. The server cannot find the requested item. This can also mean that the endpoint is valid but the resource does not exist.
500 Internal Server Error. The server has encountered an unknown error.
502 Bad Gateway. The server is working as a gateway to handle the request and received an invalid response.
503 Service Unavailable. The server is not ready to handle the request.
504 Gateway Timeout. The server is acting as a gateway and cannot get a response in time.