From 5fa5285733c9a573a9ec2d5d935ef87e702789c7 Mon Sep 17 00:00:00 2001 From: Alexandros Ntousias Date: Tue, 5 Nov 2024 15:21:04 +0200 Subject: [PATCH] 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. --- docs/references/backend/testing-tokens/create-testing-token.mdx | 2 +- docs/testing/overview.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/references/backend/testing-tokens/create-testing-token.mdx b/docs/references/backend/testing-tokens/create-testing-token.mdx index 040cfa0084..8862ac55b2 100644 --- 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 diff --git a/docs/testing/overview.mdx b/docs/testing/overview.mdx index c3d57f7197..5cc89ba58e 100644 --- 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: