This guide aims to cover the process for migrating from lower-level Turnkey SDK (i.e. @turnkey/{ http, api-key-stamper, webauthn-stamper, iframe-stamper }
) libraries, to our more recent abstractions: @turnkey/{ sdk-browser, sdk-server, sdk-react }
@turnkey/{ sdk-browser, sdk-server, sdk-react }
abstract away the details that most developers don’t need to configure, enabling you to focus more on business logic and less on configuration.
@turnkey/http
and @turnkey/api-key-stamper
. The transition to using @turnkey/sdk-server
is fairly straightforward: just bring your API key details, and you’ll be able to reduce the amount of code you need to include.
Turnkey on the client
In a browser setting, you’re most likely using @turnkey/http
and @turnkey/api-key-stamper
and/or @turnkey/iframe-stamper
. If you’re using NextJS or React in general, you’ll benefit from using @turnkey/sdk-react
.
We’ve included some details on making these transitions below:
@turnkey/http
and @turnkey/api-key-stamper
:
@turnkey/sdk-server
:
@turnkey/http
and @turnkey/webauthn-stamper
@turnkey/sdk-react
: