Route Configuration Guide
Learn how to configure routes with custom headers, method filtering, and environment-specific settings.HTTP Methods
Control which HTTP methods are allowed:Allow All Methods
By default, all methods (GET, POST, PUT, PATCH, DELETE) are allowed.Restrict Methods
- Edit your route
- Under Allowed Methods, uncheck methods you want to block
- Example: Only allow GET and POST
Header Injection
Add custom headers to requests sent to your backend:Example: Add API Key
Example: Add Authentication
{{secret:secret_name}} to inject secrets
Body Injection
Add data to the request body:Example: Add Tenant ID
Path Handling
The request path is appended verbatim to the route’s target base URL. KnoxCall does not rewrite, strip, or remove any path prefix. For example, if your target base URL ishttps://api.example.com and a client requests /api/v1/users/123, the request is forwarded to:
https://api.example.com/backend), the client path is appended to it (https://api.example.com/backend/api/v1/users/123). Query parameters from the incoming request are preserved.
Environment Configuration
Set different target URLs per environment:- Edit route
- Scroll to Environment Configuration
- For each environment:
- Development:
http://localhost:3000 - Staging:
https://staging-api.example.com - Production:
https://api.example.com
- Development:
Rate Limiting
Limit requests per client:- Enable Rate Limiting
- Set limits:
- Requests: 100
- Window: 60 (seconds)
- Burst: 120
Timeout Settings
Default timeout is 30 seconds. Contact support to adjust.Testing Configuration
After making changes:- Click Test Route
- Select environment
- Enter sample request
- View response
Need More Help?
- See the Quick Start Guide for basics
- Learn about secrets for secure credential injection
- Check troubleshooting guides for common issues
📊 Statistics
- Level: intermediate
- Time: 10 minutes
🏷️ Tags
routes, configuration, intermediate