Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 2 commits into from
Nov 12, 2024
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5fa5285
chore: Testing tokens are now enabled in production instances as well
alex-ntousias Nov 5, 2024
22b4782
Merge branch 'main' into enable-testing-tokens-in-production
victoriaxyz Nov 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/references/backend/testing-tokens/create-testing-token.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
2 changes: 1 addition & 1 deletion docs/testing/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
Loading