Endpoint: https://api.authsignal.com/v1/client

The Authsignal Client API can be used to perform challenges using different authentication methods and verify users.

This API is designed to be used if you’re not using Authsignal’s pre-built UI and are building your own web or native app UI.

​
Region selection

Use the appropriate API URL for your region.

RegionAPI URL
US (Oregon)https://api.authsignal.com/v1
AU (Sydney)https://au.api.authsignal.com/v1
EU (Dublin)https://eu.api.authsignal.com/v1

​
Authentication

The Authsignal Client API uses bearer authentication with a short-lived token obtained from the Server API or via a Server SDK.

​
1. Track an action

You should first track an action that represents what the user is doing (e.g. “signIn”) and get a token which is valid for 10 minutes.

When tracking an action to enroll an authenticator, the scope add:authenticators must be explicitly specified if the user is already enrolled with at least one authentication method. Learn more about scopes for authenticator binding.

​
2. Use bearer auth

This token can then be used to authenticate to the Client API using bearer auth.

curl https://api.authsignal.com/v1/client/user-authenticators \
  -H "Accept: application/json" \
  -H "Authorization: Bearer TOKEN_RETURNED_FROM_SERVER_API"

The authentication model is designed so you can call the Authsignal Client API directly from your web browser or mobile app (though you can also communicate via your backend where convenient). It is the same as the authentication model when using Client SDKs.

Was this page helpful?