Skip to main content
POST
/
webauthn
/
login
/
finalize
Finalize WebAuthn login
curl --request POST \
  --url https://{tenant_id}.hanko.io/webauthn/login/finalize \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "_18q6IjW09tiM4NSbsZjocUtGx00Muv5mN6LZCelCMDD...",
  "rawId": "_18q6IjW09tiM4NSbsZjocUtGx00Muv5mN6LZCelCMDD...",
  "type": "public-key",
  "response": {
    "clientDataJson": "eyJ0eXBlIjoid2ViYXV0aG4uZ2V0IiwiY2hhbGxlbmdl...",
    "authenticatorData": "SZYN5YgOjGh0NBcPZHZgW4_krrmihjLHmVzzuoMdl2MF...",
    "signature": "MEQCIHe2RXqh6dyZw1LNXgeTTxljCV_qK2ydQjp02CiF...",
    "userHandle": "rpe_EkgaSEeZG0TwzZyZJw"
  }
}
'
{
  "credential_id": "<string>",
  "user_id": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.hanko.io/llms.txt

Use this file to discover all available pages before exploring further.

Deprecated. Please use the Flow API instead. What’s the Flow API?.
Finalize a login with Webauthn using the WebAuthn API response to a navigator.credentials.get() call.
The Webauthn API uses binary data represented by ArrayBuffers for certain input/output values. The Hanko API returns these values as base64url-encoded, so they must be converted to ArrayBuffers when passed to the Webauthn API. Similarly, Webauthn API output must be converted to base64url-encoded values when passed to the Hanko API (e.g. using the webauthn-json library).

Body

application/json

WebAuthn API response to a navigator.credentials.get() call

​
id
string
Example:

"_18q6IjW09tiM4NSbsZjocUtGx00Muv5mN6LZCelCMDD..."

​
rawId
string
Example:

"_18q6IjW09tiM4NSbsZjocUtGx00Muv5mN6LZCelCMDD..."

​
type
enum<string>
Available options:
public-key
Example:

"public-key"

​
response
object

Response

Successful login

Response after a successful login with webauthn

​
credential_id
string<base64url>
​
user_id
string<uuid4>