Techniques for securing application programming interface requests using multi-party digital signatures

A non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry of a first system to execute a process, the process comprising:

• generating at least one first secret share of a plurality of secret shares based on an API secret, wherein the plurality of secret shares includes the at least one first secret share and at least one second secret share, and wherein the at least one second secret share is generated by at least one second system;
• receiving an API request;
• determining a signing policy including a first requirement that a minimum number of secret shares of the plurality of secret shares are available to sign the API request;
• validating the API request based on the signing policy and the minimum number of secret shares available to sign the API request from at least the first system and the at least one second system;
• and
• signing the API request using the at least one first secret share, wherein the API request is further signed by the at least one second system using the at least one second secret share, and wherein the API request is signed without revealing any of the at least one first secret share to the at least one second system and without revealing any of the at least one second secret share to the first system.

A system for securing application programming interface (API) requests, comprising:

• a processing circuitry;
• and
• a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to:
• generate at least one first secret share of a plurality of secret shares based on an API secret, wherein the system is a first system, wherein the plurality of secret shares includes the at least one first secret share and at least one second secret share, and wherein the at least one second secret share is generated by at least one second system;
• receive an API request;
• determine a signing policy including a first requirement that a minimum number of secret shares of the plurality of secret shares are available to sign the API request;
• validate the API request based on the signing policy and the minimum number of secret shares available to sign the API request from at least the first system and the at least one second system;
• and
• sign the API request using the at least one first secret share, wherein the API request is further signed by the at least one second system using the at least one second secret share, and wherein the API request is signed without revealing any of the at least one first secret share to the at least one second system and without revealing any of the at least one second secret share to the first system.