Diff for /documentation/tutorials/implementing_http_signatures.md
On this page, you can preview the modified document with the changes.
Note that the links within this diff are most likely broken because they are
relative to the original document or
point to another document that is not part of the changeset.
HTTP signatures
To increase the security of requests sent to the Upvest Investments API, all requests sent submitted must be signed with a signature algorithm.
## Supported versions
We currently support the following signature algorithm versions.
Supported versions
All requests sent to the Investment API must be signed. versions:
The Investment API supports the following signature algorithms:- Version
615** as defined in the IETF draft for HTTP Message Signaturesv6.
This is the default algorithm that the Investment API uses. v15](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures-15).Version
156** as defined in the IETF draft for HTTP Message Signaturesv15. v6](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures-06).
Implementation guides
We have provided tutorials on how to implement each of these. There is also a guide describing how to upgrade from v6 to v15.
'Implementing HTTP signatures v6': Learn how to implement signatures v6.
'Implementing HTTP signatures v15': Learn how to implement signatures v15.
'Upgrade HTTP signatures from v6 to v15': Learn how to upgrade from v6 to v15.
## HTTP signatures examples
We provide some code examples of how to create the necessary HTTP signatures for the Upvest Investment API.
Find out here what samples are available and how you can implement them.