fix: correct the method of linking social identities

logto-io · Jan 21, 2025 · c598361 · c598361
1 parent eb6cbcf
commit c598361
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/end-user-flows/account-settings/by-account-api.mdx b/docs/end-user-flows/account-settings/by-account-api.mdx
@@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \
 
 The `connectorData` is the data returned by the social connector after the user authorizes the application, you need to parse and get the query parameters from the `redirectUri` in your callback page, and wrap them as a JSON as the value of the `connectorData` field.
 
-Finally, you can use the `PATCH /api/my-account/identities` endpoint to link the social connection.
+Finally, you can use the `POST /api/my-account/identities` endpoint to link the social connection.
 
 ```bash
-curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \
+curl -X POST https://[tenant-id].logto.app/api/my-account/identities \
   -H 'authorization: Bearer <access_token>' \
   -H 'logto-verification-id: <verification_record_id>' \
   -H 'content-type: application/json' \