# Automating Remote Engines through APIs

A dedicated set of APIs allows you to automate the lifecycle of your Remote Engines and Remote Engine Clusters.

Get started with the Remote Engine APIs using the examples below.

Information noteNote: API requests require access tokens:

* Generate access tokens:

  * For users, generate a personal access token by following [Generating a Personal Access Token](https://help.qlik.com/talend/r/en-US/Cloud/management-console-user-guide/cloud-access-token).
  * For service accounts, generate a service access token by following [Generating a service account token](https://help.qlik.com/talend/r/en-US/Cloud/api-user-guide/generate-service-account-token).

  Once generated, a service account token expires after 30 minutes. If it expires, generate a new token using the POST method at the endpoint https://api.<env>.cloud.talend.com/security/oauth/token. For more information about generating a token, see [Generating a service account token](https://help.qlik.com/talend/r/en-US/Cloud/api-user-guide/generate-service-account-token).

To learn more about the possible actions on Remote Engines and Remote Engine Clusters available through APIs, check [Remote Engine](https://api.talend.com/apis/processing/2021-03/#section_remote-engines) section on Talend API documentation portal.

### In this section

* [Creating and pairing a Remote Engine programmatically](https://help.qlik.com/talend/en-US/remote-engine-user-guide-linux/Cloud/creating-and-pairing-remote-engine-programmatically)
* [Adding an existing Remote Engine to a Remote Engine Cluster](https://help.qlik.com/talend/en-US/remote-engine-user-guide-linux/Cloud/adding-existing-remote-engine-to-remote-engine-cluster)