Auth
Last updated
Was this helpful?
Last updated
Was this helpful?
Refreshes the access token by the refresh token.
/auth/v1/refresh
Creates new account and register the current device's key as the initial user key. This involves deploying the account on the chain you've specified.
/auth/v1/signup
The login channel the user is currently signing in/up.
firebase
firebase
, test
The access token / ID token / redirect code retrieved as a result of OAuth 2.0 Sign In. Server uses it to call the OAuth provider to verify that the client correctly finished OAuth flow, and fetches users' basic profile information such as email.
Its value differs by channel:
apple
, it's the ID token returned after finishing the SIWA process from the client.firebase
, it's the redirect code from OAuth2 Redirect URI.eyJhbGciOiJIUzI...Qedy-rosPJLzs3jArh6Vc
flow-mainnet
, flow-testnet
, ethereum-mainnet
, ethereum-goerli
, polygon-mainnet
, polygon-mumbai
The user key (usually device key / PassKey) created from the client SDK. Used as one of initial multi-sig keys for creating an account.
Sign in with two-factor authentication from other device. This is required when the user is trying to sign on the new device.
/auth/v1/signin/2fa
Finish sign in after the user authorized the request on the other device. This API will return the API credentials and account information.
/auth/v1/signin/2fa/finish
The latest 2FA request ID.
deadbeef-dead-beef-dead-beefdeadbeef
Starts SignIn Challenge. This is required when the user is trying to sign in from the device already registered.
The client should request with the public key of the device. If it's not registered,
it will raise HTTP 400 with PleaseRegisterKey
error.
Issues a random 32-byte challengeData
to the client.
The client should respond by signing the data with the device's key, within 5 minutes.
The challenge type should be specified with either passKey
or deviceKey
.
/auth/v1/signin/challenge
deviceKey
, passKey
The public key of the PassKey in client-side. Should be 64-byte hex string concatenated with [x: 32byte, y: 32byte].
Finishes sign in challenge.
The client should provide the signature of the challengeData
issued by the server.
If valid, it will return the API credentials and account information.
/auth/v1/signin/challenge/respond
deviceKey
, passKey
Request to recover the account.
/auth/v1/recover
No body