Request Lifecycle

When a caller sends a request to a proxy, RequestRocket applies the configured records in a defined order. A call can stop before reaching the target.

1. Authenticate the caller. RequestRocket checks the inbound credential.
2. Check meters and limits. Applicable meters are selected by their predicates. A limit that is already exhausted stops the call with 429 and a Retry-After header.
3. Evaluate rules. Rules on the proxy, inbound credential, target, and target credential decide whether the request is allowed.
4. Apply overrides. Matching overrides update request headers, query parameters, or body fields.
5. Run one request transform. The highest-priority matching request transform can change the relative path, method, headers, parameters, or body.
6. Call the target. RequestRocket applies the target credential and sends the request to the target.
7. Apply filters. Filters run across target credential, target, inbound credential, and proxy scopes.
8. Run one response transform. The highest-priority matching response transform can change the response.
9. Settle meters. Request-count and response-value contributions are recorded for applicable meters.
10. Record the call. The result is available through request logs and contributes to telemetry. Configured alert policies contribute to alerts.

Shared response codes are listed on Platform limits.

Next