chore: Testing tokens are now enabled in production instances as well

Previously, testing tokens were only available for dev instances. This commit updates the necessary docs to reflect that, testing tokens are available for production instances as well.
clerk · Nov 5, 2024 · 5fa5285 · 5fa5285
1 parent 78952ae
commit 5fa5285
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/references/backend/testing-tokens/create-testing-token.mdx b/docs/references/backend/testing-tokens/create-testing-token.mdx
@@ -3,7 +3,7 @@ title: '`createTestingToken()`'
 description: Use Clerk's Backend SDK to create a testing token for the instance.
 ---
 
-Creates a Testing Token for the instance. **It only works on development instances.**
+Creates a Testing Token for the instance.
 
 ```ts
 function createTestingToken(): Promise<TestingToken>

diff --git a/docs/testing/overview.mdx b/docs/testing/overview.mdx
@@ -16,7 +16,7 @@ Testing Tokens allow you to bypass bot detection mechanisms that protect Clerk a
 > [!NOTE]
 > While you can manually implement the following logic in your test suite, Clerk provides [Playwright](/docs/testing/playwright/overview) and [Cypress](/docs/testing/cypress) integrations that handle this automatically.
 
-Obtained via the [Backend API](/docs/reference/backend-api/tag/Testing-Tokens){{ target: '_blank' }}, Testing Tokens are short-lived and valid only for the specific instance for which they are issued. Testing Tokens are only available in development instances.
+Obtained via the [Backend API](/docs/reference/backend-api/tag/Testing-Tokens){{ target: '_blank' }}, Testing Tokens are short-lived and valid only for the specific instance for which they are issued.
 
 Once retrieved, include the token value in the `__clerk_testing_token` query parameter in your Frontend API requests. For example, a sign-up request using a Testing Token would look like this: