How I can call thirdpary API with using PIR

[JKBvi1]

Hello team,

Thank you for providing this example — it has been very helpful.
I have a question regarding integration:

How can I integrate a third-party API call that uses a plain text query parameter? Currently, we do not have a sufficient internal database to identify phone numbers, so we rely on external third-party services for lookup. I would like to understand how such a use case could be incorporated within this framework.

And I am not able to understand the below graph. Can you please explain this as well, how it will work

Looking forward to your guidance.

Thank you!

[karulont]

Re: plaintext query parameter

This is not possible with the current system. The incoming phone number never leaves the device. We use homomorphic encryption where, the server never gets the key to decrypt the query. So plaintext queries are not supported.

Re: OHTTP

1. Device will encapsulate ( encrypt) it's request using the gateway's public key.
2. Encapsulated request is sent to the relay.
3. Relay forwards the encapsulated request to the gateway. Note: relay does not include the IP address of the client. And secondly: Relay cannot decrypt the request to see what it is.
4. Gateway decrypts the requests and sees which target resource this request is for. However, gateway does not know which client is responsible for the request, it only knows that it came from the relay.

The backward route is similarly protected.
One can read https://www.ietf.org/rfc/rfc9458.html to learn more about Oblivious HTTP.