Using API to set up your IP allowlist without activating it

Use the POST method on the /v1/management/ip-allowlist endpoint to set up your IP allowlist with your IP and keep this list inactive.

In this example, Talend API Tester is used to issue API queries. For further information about Talend API Tester, see Talend Cloud API Tester User Guide.

If you need information about other available endpoints, see the following section about the IP allowlist API endpoints.

Procedure

If you do not have a personal access token yet in the Users tab, generate a personal access token for your account:
1. In the top-right corner, click your username.
2. Click Profile preferences > Personal access tokens > Add token.
3. Enter a token name and click Generate.
Open Talend API Tester in your browser and select POST from the Method list.
In the field next to the Method drop-down list, enter the IP allowlist endpoint to be used: https://api.<your_environment>.cloud.talend.com/v1/management/ip-allowlist
For example, your environment can be:
- ap
- eu
- us
- us-west
- au
- at if you are using this feature in an Early Adopter Program.
For more details about the available environments, see Accessing Talend Cloud applications.
In the HEADERS area, click Add header and in the name field that is displayed, enter Authorization and in the value field, enterBearer and your personal access token. Enter a whitespace to separate Bearer and your personal access token.

In the Body area, enter the following IPs:

Example

{
  "description": "description_of_your_IP_allowlist",
  "enabled": false,
  "ips": [
    {
      "description": "description_of_your_IP",
      "ip": "XXX.XX.XXX.XXX"
    }
  ]
}

Click Send to issue your request.

Results

The status code 201 is returned and your IP allowlist is set up successfully with your IP on this list. But this allowlist is not activated as the enabled parameter was set to false in the query.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here