For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
13.5kProductPricingSign inStart free trialBook a demo
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
    • Home
  • Get started
    • Quickstart
    • Introduction to feature flags
    • Unleash architecture overview
  • Core concepts
    • Overview
      • API tokens and client keys
      • Frontend API
      • Role-based access control
      • Single sign-on
      • Provisioning
      • Change requests
      • Public invite links
    • Import and export

Unleash reduces the risk of releasing new features, drives innovation by streamlining the software release process, and increases revenue by optimizing end-user experience. While we serve the needs of the world's largest, most security-conscious organizations, we are also rated the “Easiest Feature Management system to use” by G2.

GitHubGitHubLinkedInLinkedInX (Twitter)X (Twitter)SlackSlackStack OverflowStack OverflowYouTubeYouTube

Server SDKs

  • Node.js
  • Java
  • Go
  • Rust
  • Ruby
  • Python
  • .NET
  • PHP
  • All SDKs

Frontend SDKs

  • JavaScript
  • React
  • Next.js
  • Vue
  • iOS
  • Android
  • Flutter

Feature Flag use cases

  • Secure, scalable feature flags
  • Rollbacks
  • FedRAMP, SOC2, ISO2700 compliance
  • Progressive or gradual rollouts
  • Trunk-based development
  • Software kill switches
  • A/B testing
  • Feature management
  • Canary releases

Product

  • Quickstart
  • Unleash architecture
  • Pricing
  • Product vision
  • Open live demo
  • Open source
  • Enterprise feature management platform
  • Unleash vs LaunchDarkly

Support

  • Help center
  • Status
  • Changelog
Made in a cosy atmosphere in the Nordic countries.Copyright © 2026 Unleash
LogoLogo
13.5kProductPricingSign inStart free trialBook a demo
On this page
  • Overview
  • Configure the Frontend API
  • Configure cross-origin resource sharing (CORS)
  • Configure the API URL
  • Generate an API token
  • Configure the refresh interval for tokens
Core conceptsIdentity and access

Frontend API

||View as Markdown|
Was this page helpful?
Previous

Role-based access control

Next
Built with
v4.18

Overview

The Unleash Frontend API simplifies connecting client-side applications to Unleash. Unleash Edge also implements this API allowing you to scale from development environments, low-traffic applications, or internal dashboards to a production-ready scalable solution.

The Frontend API has a straightforward setup, and since it is built directly into Unleash, you don’t need to manage it. However, unlike Unleash Edge, it cannot be scaled horizontally and isn’t designed for high request volumes.

Since the Frontend API shares the same API as Unleash Edge, you can start development with the Frontend API and transition to Unleash Edge when needed.

Configure the Frontend API

Configure cross-origin resource sharing (CORS)

For web and hybrid mobile apps, allow traffic from your application’s domains.

For Unleash, you can update CORS settings in the Unleash Admin UI in Admin settings > Access control > CORS origins. For Unleash Edge, follow our command-line for CORS settings.

Configure the API URL

Point your application to the correct API endpoint: <your-unleash-instance>/api/frontend.

Generate an API token

Your application needs a frontend token to interact with the Frontend API.

Configure the refresh interval for tokens

Feature flag updates occur at a default refresh interval of 10 seconds plus a random offset (0-10 seconds) to prevent simultaneous database queries. You can customize the refresh interval using the FRONTEND_API_REFRESH_INTERVAL_MS environment variable or the frontendApi.refreshIntervalInMs configuration option in the SDK.