Introduction ============ For scenarios where a programmatic integration isn't possible, e.g where you aren't able to provide your own UI, we offer a 'Browser-based integration'. This enables a third-party application to make use of our web interface, allowing a user to place an order directly into our system. It makes use of a one-time password link that can be used to automatically sign-in the user to our system. This can be used as a standard redirect in a web application or used from a desktop application to open a web browser on the user's computer. Process flow ------------ The process flow is as follows: * Send an order request to the case endpoint, this should contain the address of the order and the users ID + secret as part of the header * Send the order reference to the OTP endpoint to recieve a URL * With the provided link perform one of the following: * Open a new Browser window with the provided URL * Redirect the user to the provided URL Authentication -------------- In order to authenticate requests to the following endpoints an authorisation header will need to be set. This will be set to a base64 encoded string which is made up of the user name & password for your user account. This is concatenated as follows : "{username}:{password}" The resulting header will look similar to the following:: Authorization: Basic {base64EncodedString} Endpoints --------- The endpoints document is availabe on the Swagger documentation page. | Case endpoint: ``_ | One-time password endpoint: ``_ Document return --------------- There are a number of options available to recieve back documents. We can either email the documents directly to the end user (providing the order was placed as the ordering user) or we can build a bespoke integration. This can be via a regular polling of our API or if required we can implement a callback that invokes your web service to return the document.