ZuploZuplo
LoginSign Up
  • Documentation
  • API Reference
Introduction
Getting Started
    Develop using the Portal
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingMCP - Quick start
    Develop Locally
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth
Concepts
Development
    CORSEnvironment VariablesBranch-Based DeploymentsTestingTroubleshootingGitOps vs TerraformCustom Code
    Local Development
    Guides
      Advanced Path MatchingAPI VersioningOpenAPI Server URLsConvert URLs to OpenAPIOpenAPI Extension DataPath Modification ScriptsOpenAPI OverlaysCanary Routing for EmployeesGeolocation Backend RoutingUser-Based Backend RoutingBypass a PolicyTesting GraphQL QueriesHealth ChecksPerformance TestingTroubleshooting Slow ResponsesNon-Standard PortsHandling FormDataS3 Signed URL UploadsCheck IP AddressLazy Load ConfigurationSharing Code Across ProjectsBackstage IntegrationGitHub Action Automation
Policies
Handlers
API Keys
MCP Server
MCP Gateway
AI Gateway
Developer Portal
Monetization
Deploying & Source Control
Observability
Networking & Infrastructure
Account Management
Programming API
Build with AI
Zuplo CLI
Migration Guides
Platform LimitsSecuritySupportTrust & ComplianceChangelog
powered by Zudoku
Guides

OpenAPI Server URLs in Zuplo

When working with OpenAPI specifications in Zuplo, it's important to understand how server URLs are handled across different environments.

Automatic Server URL Overwriting

Zuplo automatically overwrites the server URLs in your OpenAPI specification files with the URL of the current environment. This automatic behavior ensures that:

  • You don't need to manually update server URLs when creating new branches
  • Each environment uses its correct API endpoint
  • The developer portal always displays the appropriate URL for that environment

Default Behavior

By default, every Zuplo environment receives its own unique API URL in the format:

Code
https://[environment-name].zuplo.app

This URL is automatically reflected in:

  • The OpenAPI specification file
  • The developer portal for that environment
  • All API documentation

Custom Domains

If you need to use a custom domain instead of the default Zuplo URL, you can configure one on a per-environment basis. When a custom domain is configured:

  • The OpenAPI server URL will show your custom domain (for example, developer-dev.accuweather.com)
  • The developer portal will display the custom domain
  • All documentation will reflect the custom domain URL

Important Considerations

  • The server URL specified in your original OpenAPI file is never used directly
  • Each environment maintains its own server URL configuration
  • Changes to custom domains require configuration through Zuplo support or the API
  • Cache invalidation may be needed when switching from direct Zuplo URLs to custom domains served through CDNs

For assistance with custom domain configuration, please contact Zuplo support.

Edit this page
Last modified on November 17, 2025
API VersioningConvert URLs to OpenAPI
On this page
  • Automatic Server URL Overwriting
  • Default Behavior
  • Custom Domains
  • Important Considerations