Skip to main content

​
What are Routes?

A route is a smart proxy that forwards API requests from your clients to your backend services. Think of it as a secure middleman that adds security, monitoring, and control.

​
The Basic Concept

Instead of calling your backend directly, clients call KnoxCall. KnoxCall validates the request, applies security rules, injects secrets, logs everything, then forwards to your backend.

​
Why Use Routes?

Routes solve common API problems: ✅ Hide backend URLs - Clients don’t know your real backend URLs ✅ Centralize credentials - API keys stored securely, not in code ✅ Monitor everything - Log all requests and responses ✅ Add security - Rate limiting, IP whitelisting, signatures ✅ Manage environments - Different configs for dev/staging/prod

​
How It Works

Step 1: Client makes request
Step 2: KnoxCall processes
  • Validates API key or IP address
  • Checks permissions
  • Injects secrets (like API keys)
  • Applies rate limits
Step 3: Forwards to backend
Step 4: Returns response
  • Logs request and response
  • Triggers alerts if needed
  • Returns to client

​
Required Headers

Every request needs:
And either:

​
URL Structure

  • Subdomain: Your tenant slug — identifies your tenant (shown in dashboard)
  • Path: Passed through to backend unchanged

​
Common Use Cases

​
Webhook Forwarding

​
API Proxy

​
Microservices

​
Quick Example

1. Create a route:
  • Name: my-api
  • Target: https://api.example.com
2. Make a request:
3. KnoxCall forwards to:
That’s it! Your route is working.

​
What’s Next?

Create Your First Route

Step-by-step guide to create a route

Route Configuration

Configure headers, secrets, and more

Testing Routes

Test your routes with curl

Advanced Features

Rate limiting, method configs, transformations
Keep it simple: Start with a basic route, then add advanced features as needed.