RequestRocket Documentation
Guides

Proxies

Learn how to create and manage proxies that connect your applications to target APIs

Proxies

A Proxy in RequestRocket is a service that sits between your application and a target API service. It manages the routing, authentication, and transformation of requests between your application and the target API.

Understanding Proxies

Each proxy configuration requires three main components:

  • Proxy Credential: The credential your application uses to authenticate with the proxy
  • Target: The destination API service you want to connect to
  • Target Credential: The credential used to authenticate with the target service

Using Your Proxy

Once your proxy is configured, you can start making requests:

Ensure Proxy is Active

Set the proxy status to "Active" in the dashboard.

Copy the Base URL

The Base URL is provided in the proxy details after creation.

Make Requests

Make requests to the Base URL using your proxy credential to authenticate.

Request Flow

The proxy will:

  1. Authenticate your request using the proxy credential
  2. Apply any authorization rules
  3. Forward the request to the target using the target credential
  4. Return the target's response to your application

The format of your proxy Base URL varies based on the region and proxy credential type. It will look something like: https://{region}.requestrocket.io/api/{proxyId}

Creating Proxies

To create a new proxy:

Go to the Proxies section in the RequestRocket dashboard.

Create New Proxy

Click the "Create" button.

Configure General Settings

Proxy Name: Choose a descriptive name for your proxy.

Examples:

  • customer-api-production
  • payment-gateway-staging
  • internal-auth-dev

Active Status: Toggle to enable or disable the proxy.

  • Active: The proxy will process requests
  • Inactive: The proxy will not process requests (useful for maintenance)

Configure Fixed Settings

Region: Select the region where the proxy will be deployed.

Once set, the region cannot be changed. All components (credentials and target) must be in the same region.

After creation, you'll receive a Base URL that your application will use to make requests.

Configure Proxy Settings

Proxy Credential: Select the credential your application will use to authenticate with the proxy.

  • Must be a proxy-type credential
  • Must be in the same region as the proxy
  • Click "New" to create a new proxy credential if needed

Target: Select the target API service.

  • Must be configured in the same region as the proxy
  • Click "New" to create a new target if needed

Target Credential: Select the credential for authenticating with the target.

  • Must be a target-type credential
  • Must be in the same region as the proxy
  • Click "New" to create a new target credential if needed

Save Proxy

Click "Save" to create the proxy and generate your Base URL.

Making Requests to Your Proxy

Proxy API (Synchronous)

For immediate, synchronous responses:

curl -X GET "https://{Your_Proxy_Base_URL}/{target_path}" \
  -H "Content-Type: application/json" \
  -H "Authorization: {Your_Proxy_Credential}"

Async API

For asynchronous processing with retry:

curl -X POST "https://{Your_Async_Base_URL}/{target_path}" \
  -H "Content-Type: application/json" \
  -H "Authorization: {Your_Proxy_Credential}" \
  -d '{"your": "payload"}'

Learn more about API endpoints →

Understanding Response Headers

RequestRocket adds these headers to all proxy responses:

requestrocket-proxy-code

Values:

  • proxy-access-granted: Proxy authentication successful
  • proxy-access-denied: Proxy authentication failed

requestrocket-proxy-message

Provides a description of the proxy code.

If you see proxy-access-granted but still get an error response, the problem is NOT with the proxy credential. Check:

  1. The target URL is correct
  2. Your request format is valid for the target API
  3. Your target credential is correct

Error Response Analysis

proxy-access-denied + Error Response:

  • Issue: Proxy credential is invalid or incorrect proxyId
  • Solution: Verify your proxy credential and proxy URL

proxy-access-granted + Error Response:

  • Issue: Target URL, request format, or target credential
  • Solution: Check target configuration and credentials

500 Error without headers:

  • Issue: Internal RequestRocket error
  • Solution: Contact support immediately

Important Notes

Regional Constraints

All components of a proxy must be in the same region:

  • Proxy credential
  • Target credential
  • Target
  • Proxy itself

Consider your application's geographic requirements when selecting a region. Create multiple proxies in different regions if needed for global coverage.

Proxy Management

Editing Proxies:

  • You can edit proxy settings after creation
  • Change credentials and targets as needed
  • The proxy's region and Base URL cannot be changed

Deleting Proxies:

  • Deleting a proxy will not affect its associated credentials or targets
  • You can recreate proxies using existing credentials and targets
  • Associated authorization rules will be deleted

Active/Inactive Status:

  • Inactive proxies will reject all requests
  • Use this for maintenance windows or testing
  • No data is lost when toggling status

Managing Proxies

The Proxies dashboard provides comprehensive management features:

View All Proxies

  • See all configured proxies
  • Filter by region and status
  • Sort by creation date or name
  • View proxy configurations

Monitor Activity

  • Track request volume
  • View success/error rates
  • Monitor response times
  • Access detailed request logs

Edit Configuration

  • Update proxy name
  • Change active status
  • Switch credentials
  • Update target assignments
  • Modify authorization rules

Visual Mapping

  • Geographic distribution of proxies
  • Regional deployment overview
  • Connection visualization

Troubleshooting

Cannot Create Proxy

Issue: "All components must be in the same region"

Solution: Ensure proxy credential, target credential, and target are all in the same region.

Proxy Access Denied

Issue: Receiving proxy-access-denied in responses

Check:

  1. Verify you're using the correct proxy credential
  2. Check the credential format matches the auth type
  3. Ensure the proxyId in the URL is correct
  4. Verify the credential hasn't been deleted

Target Errors

Issue: proxy-access-granted but getting 401/403/404 errors

Check:

  1. Verify target URL is correct
  2. Check target credential is valid
  3. Ensure request paths are correct
  4. Verify target API is accessible

Proxy Inactive

Issue: All requests failing

Check:

  1. Verify proxy is set to "Active" status
  2. Check if proxy was recently modified
  3. Ensure credentials haven't been deleted

Next Steps

On this page