Synchronous requests

You can use synchronous requests primarily for REQUEST or RESPOND API actions. The main reason for sending a synchronous request is to query data from or write data to your connection's EHR system. The endpoint that requests the data waits for a response from the endpoint the query is sent to.

Responses to REQUEST

Like everything else in life, some requests work out and others don’t. We’re happy to let you know the fate of your request either way, and we have some details about each scenario below.

For synchronous requests, you receive one response with two parts: the HTTP status code from Redox and the results of your request from the endpoint. 

There are three scenarios for the response. 

Related logs

For any of these scenarios, you can check the related log for details after you receive a response. The related log object and ID is located in the Meta.Logs[].ID array in the body of the response. You can search for any of the log IDs in the dashboard or via the Platform API. Learn more about logs.

Responses to RESPOND

When you receive a synchronous request from your integration, we wait for you to send back a response with the results of their request. Then, we return it to your integration in the format indicated in their request.