ZuploZuplo
LoginStart for Free
  • Documentation
  • API Reference
Getting Started
    Develop in the portal
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingDynamic MCP Server - Quickstart
    Develop locally with the CLI
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingDynamic MCP Server - Quickstart
Concepts
API Management
    Overview
    API Keys
    Rate Limiting
    Caching
    GraphQL
    Monetization
    Policies
      Overview
      Authentication
      Authorization
      Security & Validation
      Metrics, Billing & Quotas
      Testing
      Request Modification
        Remove Request HeadersClear Request HeadersChange MethodForm Data to JSONRemove Query ParametersAdd or Set Request HeadersSet BodyAdd or Set Query ParametersQuery Parameter to Header
      Response Modification
      Upstream Authentication
      GraphQL
      Caching
      Other
      Guides
    Handlers
AI Gateway
MCP Gateway
MCP Server
Developer Portal
Development
Deploying & Source Control
Analytics
Observability
Networking & Infrastructure
Account Management
Programming API
Build with AI
Zuplo CLI
Migration Guides
Platform LimitsVersion Support PolicySecuritySupportTrust & ComplianceChangelog
powered by Zuplo
Request Modification

Add or Set Request Headers Policy

The set header policy adds a header to the request in the inbound pipeline. This can be used to set a security header required by the downstream service.

Configuration

The configuration shows how to configure the policy in the 'policies.json' document.

Code
{ "name": "my-set-headers-inbound-policy", "policyType": "set-headers-inbound", "handler": { "export": "SetHeadersInboundPolicy", "module": "$import(@zuplo/runtime)", "options": { "headers": [ { "name": "my-custom-header", "value": "test" } ] } } }

Policy Configuration

  • name <string> - The name of your policy instance. This is used as a reference in your routes.
  • policyType <string> - The identifier of the policy. This is used by the Zuplo UI. Value should be set-headers-inbound.
  • handler.export <string> - The name of the exported type. Value should be SetHeadersInboundPolicy.
  • handler.module <string> - The module containing the policy. Value should be $import(@zuplo/runtime).
  • handler.options <object> - The options for this policy. See Policy Options below.

Policy Options

The options for this policy are specified below. All properties are optional unless specifically marked as required.

  • headers (required) <object[]> - An array of headers to set in the request. By default, headers will be overwritten if they already exists in the request, specify the overwrite property to change this behavior.
    • name (required) <string> - The name of the header.
    • value (required) <string> - The value of the header.
    • overwrite <boolean> - Overwrite the value if the header is already present in the request. Defaults to true.

Using the Policy

An example for using this policy is if your backend service uses basic authentication you might use this policy to attach the Basic auth header to the request:

Code
{ "export": "SetHeadersInboundPolicy", "module": "$import(@zuplo/runtime)", "options": { "headers": [ { "name": "Authorization", "value": "Basic DIGEST_HERE", "overwrite": true } ] } }

When doing this, you most likely want to set the secret as an environment variable, which can be accessed in the policy as follows

Code
{ "export": "SetHeadersInboundPolicy", "module": "$import(@zuplo/runtime)", "options": { "headers": [ { "name": "Authorization", "value": "$env(BASIC_AUTHORIZATION_HEADER_VALUE)", "overwrite": true } ] } }

And you would set the environment variable BASIC_AUTHORIZATION_HEADER_VALUE to Basic DIGEST_HERE.

Read more about how policies work

Edit this page
Last modified on September 14, 2026
Remove Query ParametersSet Body
On this page
  • Configuration
    • Policy Configuration
    • Policy Options
  • Using the Policy
JSON
JSON
JSON