Config Source: Cloudflare KV
Load config from KV when you need runtime-managed routing without baking config into the bundle. This lets you update routing rules, add paths, or change
Last updated
Load config from KV when you need runtime-managed routing without baking config into the bundle. This lets you update routing rules, add paths, or change
Load config from KV when you need runtime-managed routing without baking config into the bundle. This lets you update routing rules, add paths, or change integrations without redeploying the worker. Use KV config when your team needs to ship routing changes independently from code changes.
Last reviewed: 2026-03-06
Use the config reference when you need to understand the shape, source, or validation behavior of the gateway JSON configuration. The config file is the single source of truth for all routing, auth, CORS, and integration behavior in the gateway.
The config schema (api-config.schema.json) defines every valid field, type, and default. Use it with your editor for autocompletion and validation before deploying.
Config can be loaded from three sources: a local JSON file bundled with the worker, a Cloudflare KV namespace, or the SAG_API_CONFIG_JSON environment variable. The gateway checks them in that order.
Strict mode rejects any config with unknown fields or type mismatches at startup, returning a 500 error. Compatibility mode logs warnings but allows the worker to start.
Legacy key normalization automatically converts old field names (like http to paths and servicesBindings to serviceBindings) so older configs continue to work during migration.
wrangler kv:key put --binding=CONFIG api-config.json ./src/api-config.json
wrangler deployThis snippet writes the local config file into a KV namespace using the Wrangler CLI. The --binding=CONFIG flag must match the KV namespace binding in your wrangler.toml, and the key api-config.json is the default key the gateway reads.
If the worker starts but routes return 404, check which config source the gateway loaded -- add a health route to each source so you can identify which one is active.
If strict mode rejects your config, run the JSON against api-config.schema.json locally with a JSON schema validator to see the exact validation errors.
If legacy key normalization is not converting a field, confirm you are running a version of the gateway that supports that alias -- check the CHANGELOG for the normalization version.
If KV config changes are not reflected after updating, remember that Workers cache KV reads. Redeploy the worker or wait for the cache TTL to expire.
Last updated