Setting up HTTP message signing Proxy

In order to communicate with the Upvest Investment API, it is necessary for every HTTP request you make to carry a cryptographic signature in its header.

   Install and configure our HTTP Signing Proxy

We provide an HTTP Signing Proxy service that you can use with tools like Postman and Curl to allow you to interact with the Upvest Investment API for initial exploration. You should not use this proxy in production.

To install and set up a local HTTP signing proxy, follow the instructions in the README file that you'll find in the project repository on GitHub.

   Plan to implement HTTP message signing in your own software

For your product to communicate with our API, you will have to implement HTTP message signatures for all requests. We have a separate tutorial that guides you through the signature process. Using that example, along with our sample implementations and technical reference documentation, your engineers should be able to implement signing within your product.

If you have installed the HTTP signing proxy in Step 1, you may move on with the "Getting Started" tutorial without having completed the implementation of HTTP Message Signing within your project. It is important that you plan for your engineers to work on HTTP message signing at the beginning of your project.

   HTTP Message Signature established!

You should have set up HTTP message signatures via the HTTP Signature Proxy, and have a plan to implement HTTP message signatures within your software.

Next step

Return to the Getting Started Tutorial and continue at "Setup complete".