Authentication

The gateway accepts two ways to prove a request is yours. Use whichever suits your infrastructure — you can mix them on one account.

#Username and password

The default. Send your proxy credentials with every request, usually embedded in the proxy URL:

curl -x "http://USERNAME:PASSWORD@gate.riftip.com:7777" https://example.com

Options such as network, location and session are appended to the username, never the password. See Geo-targeting for the full list.

#Sub-users

Create sub-users under Dashboard → Sub-users to give each team, project or customer their own credentials with their own traffic limits. Revoking a sub-user stops its traffic immediately without affecting anyone else. You can also manage them with the Sub-users API.

#IP allowlisting

If your traffic comes from fixed servers, add their IPs under Dashboard → Allowlist. Requests from those IPs are accepted without credentials:

curl -x "http://gate.riftip.com:7777" https://example.com

Without a username, there's nowhere to put options — so allowlisted requests use your account's default network and location, set in the dashboard. To target per request, use credentials instead.

#Ports and protocols

HTTPS targets are tunnelled end to end: the gateway never sees your request or response content.