Config · Customer documentation

What you prepare

The keys/values your app will read; never include secrets.

Steps in the workspace

1. 01Create a configuration project.
2. 02Set configuration keys and values.
3. 03Fetch the public URL from your app.

Example request / integration

Publish maintenance=true and let the app GET it to toggle a maintenance banner.

# Create a project; set maintenance to true in its workspace.
curl --fail-with-body "$FLAGS_URL"
# Example response: {"project":"My app","flags":{"maintenance":true}}
# Do not put passwords in published flag values.

Examples use placeholders: replace $BASE_URL, $SESSION_TOKEN and issued URLs with real values. Never publish session tokens or API keys in a webpage or repository.

Management API entry point

POST /api/picosvc/flags/projects

Project name, key, JSON value, and enabled state.

A public JSON endpoint returning enabled values.

What it does not do

No user targeting, percentage rollouts, or A/B experiments.

Feature comparison and sources

Targeting and rollout：Return enabled values per project.

LaunchDarkly：Documents attribute-based targeting and percentage rollouts.