Skip to content

Update old openapi redocly link to scalar #3113

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

Draft
NWylynko wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update old openapi redocly link to scalar #3113

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/guides/development/migrating/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Each of these have trade-offs you'll need to consider for your application and i

With basic export/import, you're taking an export from your previous tool and importing data into Clerk. The most common way to handle this is by making use of the [`CreateUser`](/docs/reference/backend-api/tag/users/post/users){{ target: '_blank' }} Backend API endpoint. It's important to note that the `CreateUser` endpoint is rate limited. For more information, see the [guide on rate limits](/docs/guides/how-clerk-works/system-limits#backend-api-requests).

You'll also need to provide your `password_hasher` value (the hashing algorithm used to generate the password digest) and in some instances Clerk will transparently upgrade your users' password hashes to the more secure Bcrypt hashing algorithm. More details on this topic are available in the [Backend API reference docs](/docs/reference/backend-api/tag/Users#operation/CreateUser!path=password_hasher\&t=request){{ target: '_blank' }}.
You'll also need to provide your `password_hasher` value (the hashing algorithm used to generate the password digest) and in some instances Clerk will transparently upgrade your users' password hashes to the more secure Bcrypt hashing algorithm. More details on this topic are available in the [Backend API reference docs](/docs/reference/backend-api/tag/users/post/users.body.password_hasher#tag/users/post/users){{ target: '_blank' }}.
Copy link
Copy Markdown
Member

@alexisintech alexisintech Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it didnt lead me anywhere

Image

Copy link
Copy Markdown
Member

@alexisintech alexisintech Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think it exists anymore https://clerk.com/docs/reference/backend-api/tag/users/post/users#tag/users/post/users


### Considerations

Expand Down