Migration from Legacy Headers
Following the rebranding pass, the default gateway headers and key prefixes have been updated from apishield to selixes. Although the gateway backend retains native backward compatibility to prevent breaking changes for live clients, we recommend updating all scripts and environment configurations to the new standard.
Header & API Key Reference Map
Use the following mapping table to update your configuration schemas:
| Legacy Key / Header | New Selixes Standard (Recommended) | Purpose |
|---|---|---|
apishield_live_... | selixes_live_... | Gateway Authorization Keys |
x-apishield-max-session-cost | x-selixes-max-session-cost | Session Spend Capping (USD) |
x-apishield-max-concurrent-calls | x-selixes-max-concurrent-calls | Concurrency Rate Limiting |
x-apishield-pii-scrubbing | x-selixes-pii-scrubbing | PII Masking at the Edge |
Backward Compatibility Notice
To ensure uninterrupted runtime for legacy applications, the gateway interceptor checks for x-apishield-* parameters if the equivalent x-selixes-* header is not provided. Both systems operate in parallel on the gateway backend, and existing API keys prefixed with apishield_live_ remain completely valid.