diff --git a/docs/tutorials/github-action-data-masking-part1.mdx b/docs/tutorials/github-action-data-masking-part1.mdx
index e92e6ace..bca52213 100644
--- a/docs/tutorials/github-action-data-masking-part1.mdx
+++ b/docs/tutorials/github-action-data-masking-part1.mdx
@@ -103,7 +103,7 @@ Go to **Data Access > Semantic Types** and click **Add**. You can create a new s
 Find the step `Apply semantic type`, which will apply the semantic type to the database via API. All the masking algorithms should be defined in one file in the root directory as `masking/semantic-type.json`.
 
 ```bash
-response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/settings/bb.workspace.semantic-types?allow_missing=true" \
+response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/settings/SEMANTIC_TYPES" \
    --header "Authorization: Bearer ${BYTEBASE_TOKEN}" \
    --header "Content-Type: application/json" \
    --data @"$CHANGED_FILE")
@@ -126,7 +126,7 @@ Go to **Data Access > Global Masking** and click **Add**. You can create a new g
 Find the step `Apply global masking rule`, which will apply the global masking rule to the database via API. All the global masking rules should be defined in one file in the root directory as `masking/global-masking-rule.json`. The code it calls Bytebase API is as follows:
 
 ```bash
-response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/policies/masking_rule?allow_missing=true&update_mask=payload" \
+response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/workspaces/-/policies/masking_rule?allowMissing=true&updateMask=payload" \
    --header "Authorization: Bearer ${BYTEBASE_TOKEN}" \
    --header "Content-Type: application/json" \
    --data @"$CHANGED_FILE")
diff --git a/docs/tutorials/github-action-data-masking-part2.mdx b/docs/tutorials/github-action-data-masking-part2.mdx
index 7fed7e2b..aa28a8f0 100644
--- a/docs/tutorials/github-action-data-masking-part2.mdx
+++ b/docs/tutorials/github-action-data-masking-part2.mdx
@@ -73,16 +73,16 @@ Go to a project page, then click **Manage > Masking Exemptions**, you can grant
 
 ### In GitHub Workflow
 
-Find the step `Apply masking exception`, which will apply the masking exception to the database and the process is similar, the code it calls Bytebase API is as follows:
+Find the step `Apply masking exemption`, which will apply the masking exemption to the database and the process is similar, the code it calls Bytebase API is as follows:
 
 ```bash
-response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/projects/${PROJECT_NAME}/policies/masking_exception?allow_missing=true&update_mask=payload" \
+response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/projects/${PROJECT_NAME}/policies/masking_exemption?allowMissing=true&updateMask=payload" \
    --header "Authorization: Bearer ${BYTEBASE_TOKEN}" \
    --header "Content-Type: application/json" \
    --data @"$CHANGED_FILE")
 ```
 
-By changing file `masking/projects/**/masking-exception.json`, create a PR and then merge, the change will be applied.
+By changing file `masking/projects/**/masking-exemption.json`, create a PR and then merge, the change will be applied.
 
 Log in Bytebase console, go to the project `Sample Project`, click **Manage > Masking Exemptions**, you can see the masking exemption is applied.
 
diff --git a/docs/tutorials/github-action-data-masking-part3.mdx b/docs/tutorials/github-action-data-masking-part3.mdx
index 2f342515..f50750c0 100644
--- a/docs/tutorials/github-action-data-masking-part3.mdx
+++ b/docs/tutorials/github-action-data-masking-part3.mdx
@@ -46,10 +46,10 @@ Go to **Data Access > Data Classification**, you can upload the classification f
 
 ### In GitHub Workflow
 
-Find the step `Apply classification`, which will apply the classification to the database via API. All the classifications should be defined in one file in the root directory as `masking/classification.json`. The code it calls Bytebase API is as follows:
+Find the step `Apply classification`, which will apply the classification to the database via API. All the classifications should be defined in one file in the root directory as `masking/data-classification.json`. The code it calls Bytebase API is as follows:
 
 ```bash
-response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/settings/bb.workspace.classification" \
+response=$(curl -s -w "\n%{http_code}" --request PATCH "${BYTEBASE_API_URL}/settings/DATA_CLASSIFICATION" \
    --header "Authorization: Bearer ${BYTEBASE_TOKEN}" \
    --header "Content-Type: application/json" \
    --data @"$CHANGED_FILE")