For the complete documentation index, see llms.txt. This page is also available as Markdown.

Remote Control API

The Remote Control API lets you create credentials to programmatically manage your Feature Experimentation account without platform access.

What you can manage:

  • Campaigns

  • Variations and variation groups

  • Flags

  • Folders

  • Targeting keys

  • Users

Accessing Remote Control API

To access the Remote Control API page, go to:

The page displays the list of generated credentials. From there, you can create new credentials, view their details, or revoke them.

Permissions

Configuration

Generating new credentials

From the Remote Control API page:

  1. Click the button to create a new access.

  2. Enter a name for your access.

  3. Select the environment(s) you want the credentials to act on.

  4. Select the action(s) you want to authorize.

  5. Click Generate API.

A pop-up appears displaying your clientId and clientSecret.

If you lose your credentials or suspect misuse, you can revoke them and generate new ones.

Managing credentials

All previously generated accesses are displayed in a list view. To view the details of a generated access:

  • Click on the corresponding row.

A side panel opens on the right side of the screen, displaying:

  • Creator information

  • Creation date

  • Associated environment

  • List of authorized actions

This lets you review the exact permissions that were granted.

Revoking an access

To revoke an access:

  • Hover over the corresponding row in the list.

  • Click Revoke.

For Developers

Ready to integrate the Remote Control API into your workflows?

Developer documentation: https://docs.developers.flagship.io/reference/authorization

Getting started

To use the API:

  1. Create an application and select the required scopes.

  2. Generate an API token.

  3. Call the API with Authorization: Bearer <your_token>.

Each application has fixed scopes. If you need additional ones, create a new application. You can find the required scope in each route’s documentation.

Last updated

Was this helpful?