> 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
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)
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
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 %}
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**.
{% hint style="danger" %}
If you revoke an access, it becomes permanently invalid. **Any service using these credentials will stop working immediately.**
You will need to create a new access and update your integrations with the new `clientId` and `clientSecret`.
{% endhint %}
### For Developers
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 `.
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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentation-settings/remote-control-api.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.