From f4404f66b83f9737a22e9f18acd432ba5d1d278e Mon Sep 17 00:00:00 2001 From: Tuan Dang Date: Tue, 13 Jun 2023 11:30:47 +0100 Subject: [PATCH] Correct link to E2EE API usage example --- docs/documentation/getting-started/api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/getting-started/api.mdx b/docs/documentation/getting-started/api.mdx index 7bcb2d76a..279982911 100644 --- a/docs/documentation/getting-started/api.mdx +++ b/docs/documentation/getting-started/api.mdx @@ -15,7 +15,7 @@ To keep it simple, we're going to fetch secrets from the API with **End-to-End E It's possible to use the API with **E2EE** enabled but this means learning about how encryption works with Infisical and performing client-side encryption/decryption operations yourself. yourself. - If **E2EE** is a must for your team, we recommend either using one of the [Infisical SDKs](/documentation/getting-started/sdks) or checking out the [examples for E2EE](/api-reference/overview/examples/e2ee-enabled). + If **E2EE** is a must for your team, we recommend either using one of the [Infisical SDKs](/documentation/getting-started/sdks) or checking out the [examples for E2EE](/api-reference/overview/examples/e2ee-disabled). ## Configuration