diff --git a/docs/src/create-apps/source-operations.md b/docs/src/create-apps/source-operations.md
index 018224cf59..3ee800798e 100644
--- a/docs/src/create-apps/source-operations.md
+++ b/docs/src/create-apps/source-operations.md
@@ -162,7 +162,7 @@ You can use cron to automatically run your source operations.
 {{< note >}}
 
 To run automated source operations using cron, you need to use [an API token](../administration/cli/api-tokens.md)
-with the [CLI installed](../administration/cli/api-tokens.md#on-a-platformsh-environment) in your app container.
+with the [CLI installed](../administration/cli/api-tokens.md#authenticate-in-a-platformsh-environment) in your app container.
 
 {{< /note >}}
 
diff --git a/docs/src/development/local/ddev.md b/docs/src/development/local/ddev.md
index 1330e83a11..a8b5d149e9 100644
--- a/docs/src/development/local/ddev.md
+++ b/docs/src/development/local/ddev.md
@@ -48,7 +48,7 @@ Your project should start running, though without any of the data from your Plat
 
 To connect DDEV with your Platform.sh account, use a Platform.sh API token.
 
-1. [Create an API token](../../administration/cli/api-tokens.md#get-a-token) in the Console.
+1. [Create an API token](../../administration/cli/api-tokens.md#2-create-a-platformsh-api-token) in the Console.
 2. Add the token to your DDEV configuration.
    You can do so globally (easiest for most people):
 
diff --git a/docs/src/development/local/docksal.md b/docs/src/development/local/docksal.md
index 2f6c1a4ac7..cedd927216 100644
--- a/docs/src/development/local/docksal.md
+++ b/docs/src/development/local/docksal.md
@@ -33,7 +33,7 @@ See all [restrictions on the projects directory](https://docs.docksal.io/getting
 
 To connect Docksal with your Platform.sh account, use a Platform.sh API token.
 
-1. [Create an API token](../../administration/cli/api-tokens.md#get-a-token) in the Console.
+1. [Create an API token](../../administration/cli/api-tokens.md#2-create-a-platformsh-api-token) in the Console.
 2. Add the token to your Docksal configuration by running this command:
 
    ```bash
diff --git a/docs/src/development/local/lando.md b/docs/src/development/local/lando.md
index 2fcfbb21c2..431683b136 100644
--- a/docs/src/development/local/lando.md
+++ b/docs/src/development/local/lando.md
@@ -35,7 +35,7 @@ Follow the [Lando installation instructions](https://docs.lando.dev/getting-star
 
 ## 2. Create an access token
 
-To authorize Lando to communicate with Platform.sh, create an [API token](../../administration/cli/api-tokens.md#get-a-token).
+To authorize Lando to communicate with Platform.sh, create an [API token](../../administration/cli/api-tokens.md#2-create-a-platformsh-api-token).
 Copy the value.
 
 ## 3. Initialize Lando
diff --git a/docs/src/environments/backup.md b/docs/src/environments/backup.md
index 6c00524ced..eba6d9ea01 100644
--- a/docs/src/environments/backup.md
+++ b/docs/src/environments/backup.md
@@ -163,7 +163,7 @@ highlight=false
 
 You can also automate the process of creating manual backups through [cron jobs](../create-apps/app-reference.md#crons).
 The cron job uses the CLI command to back up the environment.
-It requires you to [set up the CLI on the environment with an API token](../administration/cli/api-tokens.md#on-a-platformsh-environment).
+It requires you to [set up the CLI on the environment with an API token](../administration/cli/api-tokens.md#authenticate-in-a-platformsh-environment).
 
 Although this process is automated,
 backups created in this way count as manual for the [backup schedule](#backup-schedule).