RequestRocket Documentation
Guides

Targets

Learn how to create and manage API targets in RequestRocket

Targets

Targets in RequestRocket represent the destination APIs that you want to connect to. A target defines the base URL configuration needed to reach and interact with your API endpoints.

Understanding Targets

A target is the destination of your API requests and serves as a fundamental building block in RequestRocket's proxy architecture. Each target configuration includes:

  • Base URL: The root endpoint of your API
  • Regional Configuration: The AWS region where the target is deployed
  • Associated Proxies: Links to proxies using this target

Targets are reusable - you can use the same target configuration across multiple proxies with different credentials or authorization rules.

Creating Targets

To create a new target:

Go to the Targets section in the RequestRocket dashboard.

Create New Target

Click the "Create" button.

Enter General Settings

Name: Choose a descriptive name for your target that helps identify its purpose.

Examples:

  • stripe-api
  • internal-user-service
  • external-payment-gateway

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

Once set, the region cannot be changed. You may need to create multiple targets in different regions if required.

Base URL: The root URL of your API (e.g., https://api.example.com)

Requirements:

  • Must include the protocol (https://)
  • Can include a base path if required (e.g., https://api.example.com/v2)
  • May include trailing slash

Test Path (Optional): A default path appended to the base URL when testing credentials against this target (e.g., /health or /api/v1/status).

This value pre-populates the path field in the credential tester when you select this target — saving you from re-entering it every time. A lightweight endpoint such as a health check is ideal.

Save Target

Click "Create" / "Update" to create / update the target.

Target Configuration Examples

REST API

Name: customer-api
Base URL: https://api.customer-service.com
Test Path: /health

Versioned API

Name: payment-api-v2
Base URL: https://payments.example.com/v2
Test Path: /status

Internal Microservice

Name: auth-service
Base URL: https://internal-auth.mycompany.com
Test Path: /ping

Third-Party Integration

Name: sendgrid-api
Base URL: https://api.sendgrid.com/v3
Test Path: /mail/send

Important Notes

Regional Constraints

Targets are constrained to the region in which they are created. When planning your architecture:

  • Deploy targets in regions close to your users for lower latency
  • Create the same target in multiple regions if required
  • Ensure all proxy components (credentials, target) are in the same region

All components of a proxy must be in the same region: proxy credential, target credential, target, and the proxy itself.

Target Management

Editing Targets:

  • You can edit target settings (name, base URL, test path) after creation
  • Changes affect all proxies using that target immediately
  • Plan carefully when modifying production targets

Deleting Targets:

  • Deleting a target will also delete all associated proxies
  • You'll receive a warning about dependent proxies before deletion
  • Consider creating a new target and assigning it to proxies that need to remain operational

Target Reuse:

  • Multiple proxies can share the same target
  • Each proxy can use different target credentials for the same target
  • Use this for A/B testing or gradual migrations, or separate proxies for different users

Troubleshooting

Connection Issues

Issue: Cannot reach target API

Check:

  1. Verify the base URL is correct and accessible
  2. Ensure the target API allows traffic from RequestRocket IPs
  3. Check if the target API is experiencing downtime
  4. Verify DNS resolution for the target domain

Authentication Failures

Issue: Getting 401/403 errors from target

Check:

  1. Verify target credential is configured correctly
  2. Ensure target credential being used hasn't expired
  3. Check that the target API hasn't changed its auth requirements
  4. Verify the target credential has necessary permissions

Path Issues

Issue: 404 errors for all requests

Check:

  1. Verify the base URL doesn't include paths that should be in the request
  2. Ensure the request path is correct
  3. Check if the target API has moved or changed its structure

Next Steps

Credentials

Create credentials for authentication

Proxies

Connect your app to the target

Rules

Set up access control

Targets

View API reference

Credentials

Learn about proxy and target credentials, how to create and manage them

Proxies

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

On this page

Targets
Understanding Targets
Creating Targets
Navigate to Targets
Create New Target
Enter General Settings
Save Target
Target Configuration Examples
REST API
Versioned API
Internal Microservice
Third-Party Integration
Important Notes
Regional Constraints
Target Management
Troubleshooting
Connection Issues
Authentication Failures
Path Issues
Next Steps