canonical: https://jentic.com/apis/reflag.com/reflag

# Reflag Management API

Feature flag Management API. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically get details of an application, list of applications. Covers 12 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get details of an application
- List of applications
- Create a flag
- Update a flag
- Monitor Reflag Management API operational status and events

## Use cases

### Developer Tools Operations

Use the Reflag Management API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including get details of an application, list of applications, list environments for application.

Example prompt: Call GET `/apps/{appId}` to get details of an application

### Automated Apps Management

Automate apps operations by combining multiple Reflag Management API endpoints. Agents can list of applications and then list environments for application in a single workflow.

Example prompt: Call GET /apps to list of applications, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Reflag Management API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get details of an application', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/apps/{appId}` | Get details of an application |
| GET | `/apps` | List of applications |
| GET | `/apps/{appId}/environments` | List environments for application |
| GET | `/apps/{appId}/environments/{envId}` | Get environment details |
| POST | `/apps/{appId}/flags` | Create a flag |
| GET | `/apps/{appId}/flags` | List flags for application |
| PATCH | `/apps/{appId}/flags/{flagId}` | Update a flag |
| GET | `/apps/{appId}/flags/{flagKey}/targeting/{envId}` | Get flag targeting for an environment |

## Key resources

- **Apps** — Operations for apps

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 71 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 60 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 76 / 100
- **View full report:** https://jentic.com/apis/reflag.com/reflag/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Reflag Management API by hand means setting its bearer token on every request and building your own retry handling against the app.reflag.com host. Through Jentic you install once, import the Reflag Management API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Reflag Management API puts the app, environment, and flag ids in the URL path (`/apps/{appId}/flags/{flagId}`), so a rule can pin your agent to one app and let it read and manage only that app's flags and environments. You choose the operations it may call, so state-changing ones like creating or patching a flag are not included unless you add them.
- **Credential handling:** Your Reflag Management API bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get details of an application' or 'list feature flags', and Jentic returns the matching Reflag Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Reflag Management API use?

The Reflag Management API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get details of an application with the Reflag Management API?

Yes. Use the GET `/apps/{appId}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Reflag Management API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get details of an application through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get details of an application'. Jentic returns the matching Reflag Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Reflag Management API have?

The Reflag Management API exposes 12 endpoints covering apps operations.

### Can I limit what my agent is allowed to do with the Reflag Management API?

Yes. Because the Reflag Management API puts the app, environment, and flag ids in the URL path such as `/apps/{appId}/flags/{flagId}`, a rule in your self-hosted Jentic One instance can pin the agent to a single app and let it read and manage only that app's flags and environments. You decide which operations the agent may call, so read-only calls like GET `/apps/{appId}` and GET `/apps/{appId}/flags` can be allowed while state-changing operations such as POST `/apps/{appId}/flags` or PATCH `/apps/{appId}/flags/{flagId}` stay out of reach unless you add them. Your own rules and stored credentials, not the agent, govern what it can do.