> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentation-settings/remote-control-api.md).

# 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  <a href="#accessing-archived-campaigns" id="accessing-archived-campaigns"></a>

To access the Remote Control API page, go to:

[**Settings > Feature Experimentation > Remote Control API**](https://app2.abtasty.com/settings/feature-experimentation/remote-control-api)

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FFxAEe4YpLmynphg855mK%2FCapture%20d%E2%80%99e%CC%81cran%202026-02-16%20a%CC%80%2011.35.35.png?alt=media&amp;token=f72a7078-c051-4915-abd3-2ac99cdd4aac" alt=""><figcaption></figcaption></figure>

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

{% hint style="warning" %}

#### Permissions

Only **Super Admin** users can access Remote Control API credentials
{% endhint %}

### Configuration

#### Generating new credentials

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2F3kXcWFhP4L2LeRMlRRCC%2FCapture%20d%E2%80%99e%CC%81cran%202026-02-16%20a%CC%80%2011.37.32.png?alt=media&amp;token=706539c3-ac50-4143-9b68-4e7e05c1a09a" alt=""><figcaption></figcaption></figure>

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`.

{% hint style="warning" %}
**You cannot retrieve these credentials once you close the pop-up.**

Copy and store your `clientId` and `clientSecret` securely. Never share them publicly.
{% endhint %}

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FLvmn0mwifk6arQnTE5xp%2FCapture%20d%E2%80%99e%CC%81cran%202026-02-16%20a%CC%80%2011.38.06.png?alt=media&amp;token=e76fc0ca-a760-4d8d-9e77-e5937432b1ac" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FB4DttlOQydEBBrtPz0oB%2FCapture%20d%E2%80%99e%CC%81cran%202026-02-16%20a%CC%80%2011.36.02.png?alt=media&amp;token=8018dc05-51b0-47bf-b69d-604dd28d0e0a" alt=""><figcaption></figcaption></figure>

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**

<div align="left"><figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FvtnwkJKKJGTbGgVbWG5V%2Fimage.png?alt=media&amp;token=83759ce1-7684-46e1-bf47-8b01bf7a74f8" alt="" width="375"><figcaption></figcaption></figure></div>

To revoke an access:

* Hover over the corresponding row in the list.
* Click **Revoke**.

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FzcKRc3BGhtHf6DKzo5Ja%2Fimage.png?alt=media&amp;token=9282c06c-2120-4376-84a4-f980e73ef1c5" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
If you revoke an access, it becomes permanently invalid. **Any service using these credentials will stop working immediately.**&#x20;

You will need to create a new access and update your integrations with the new `clientId`  and `clientSecret`.
{% endhint %}

### For Developers&#x20;

Ready to integrate the Remote Control API into your workflows?

**Developer documentation:** [**https://docs.developers.flagship.io/reference/authorization**](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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentation-settings/remote-control-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
