Auth0.js v8 Reference

Auth0.js is a client-side library for Auth0. Using auth0.js in your web apps makes it easier to do authentication and authorization with Auth0 in your web apps.

This document covers the most up-to-date version of auth0.js - version 8. If you are already using version 7, you can take a look at the v7 reference guide, or take a look at the v8 migration guide

Ready-to-go example

The example directory of the auth0.js library is a ready-to-go app that can help you to quickly and easily try out auth0.js. In order to run it, follow these quick steps:

  1. If you don't have node installed, do that now
  2. Download dependencies by running npm install from the root of this project
  3. Finally, execute npm start from the root of this project, and then browse to your app running on the node server, presumably at http://localhost:3000/example.

Setup and initialization

Now, let's get started integrating auth0.js into your project. We'll cover methods of installation, how to initialize auth0.js, signup, login, logout, and more!

Installation options

You have a few options for using auth0.js in your project. Pick one of the below depending on your needs:

Install via npm:

npm install auth0-js

Install via bower:

bower install auth0.js
<script src="bower_components/auth0.js/build/auth0.min.js"></script>

Include via our CDN:

<script src=""></script>

Note that for production use, the latest patch release (for example, 8.0.0) is recommended, rather than the latest minor release indicated above.

If you are using a bundler, you will want to install with npm i auth0-js --production --save.


Initialize a new instance of the Auth0 client as follows:

<script src=""></script>
<script type="text/javascript">
  var webAuth = new auth0.WebAuth({
    domain:       'YOUR_AUTH0_DOMAIN',
    clientID:     'YOUR_CLIENT_ID'

Available parameters

  • domain {string}: Your Auth0 account domain (ex.
  • client_id {string}: Your Auth0 client_id
  • redirectUri {string}: The default redirectUri used. Defaults to an empty string (none).
  • scope {string}: The default scope used by the application. Using scopes can allow you to return specific claims for specific fields in your request. You should read our documentation on scopes for further details about them.
  • audience {string}: The default audience used for requesting API Access.
  • responseType {string}: The default responseType used, 'token' or 'code'. Defaults to 'token', unless a redirectUri is provided, then defaults to 'code'.
  • responseMode {string}: This option is omitted by default. Can be set to 'form_post' in order to send the token or code to the redirectUri via POST.
  • _disableDeprecationWarnings {boolean}: Disables the deprecation warnings, defaults to false.


You can choose a method for login based on the type of auth you need in your application.


The authorize method can be used for logging in users via the Hosted Login Page, or via social connections, as exhibited below.

For hosted login, one must call the authorize endpoint:

  //Any additional options can go here 

For social logins, the connection will need to be specified:

  connection: 'twitter'


For popup authentication the popup.authorize method can be used.

Hosted login with popup:

  //Any additional options can go here 

And for social login with popup using authorize:

  connection: 'twitter'


To login using redirect with credentials to enterprise connections, the redirect.loginWithCredentials method is used.

  connection: 'Username-Password-Authentication',
  username: 'testuser',
  password: 'testpass',
  scope: 'openid'


To login using popup mode with credentials to enterprise connections, the popup.loginWithCredentials method is used.

  connection: 'Username-Password-Authentication',
  username: 'testuser',
  password: 'testpass',
  scope: 'openid'


The client.login method allows for non redirect auth using custom database connections, using /oauth/token.

  realm: 'tests',
  username: 'testuser',
  password: 'testpass',
  scope: 'openid profile',
  audience: 'urn:test'


The buildAuthorizeUrl method can be used to build the /authorize URL, in order to initialize a new transaction. Use this method if you want to implement browser based (passive) authentication.

// Calculate URL to redirect to
  var url = webAuth.client.buildAuthorizeUrl({
    clientID: 'YOUR_CLIENT_ID', // string
    responseType: 'token', // code or token
    redirectUri: 'https://YOUR_APP/callback',
    state: 'YOUR_STATE'
  // Redirect to url
  // ...

NOTE: The state parameter, is not required, but it is recommended. It is an opaque value that Auth0 will send back to you. This method helps prevent CSRF attacks.

Passwordless login

Passwordless authentication allows users to log in by receiving a one-time password via email or text message. The process will require you to start the Passwordless process, generating and dispatching a code to the user, (or a code within a link), followed by accepting their credentials via the verification method. That could happen in the form of a login screen which asks for their (email or phone number) and the code you just sent them. It could also be implemented in the form of a Passwordless link instead of a code sent to the user. They would simply click the link in their email or text and it would hit your endpoint and verify this data automatically using the same verification method (just without manual entry of a code by the user).

Start passwordless

The passwordlessStart method requires several options:

  • connection: a string that specifies how to send the code/link to the user. Value must be either email or sms.
  • send: a string, value must be either 'code' or 'link'. If null, a link will be sent.

In addition, one of the two following options must be sent:

  • phoneNumber: a string containing the user's phone number for delivery of a code or link via SMS.
  • email: a string containing the user's email for delivery of a code or link via email.
    connection: 'email',
    send: 'code',
    email: ''
  }, function (err,res) {
    // handle errors or continue

Verify passwordless

The passwordlessVerify method requires several options:

  • connection: a string that specifies how to send the code/link to the user. Value must be either email or sms and the same with the one used at passwordlessStart.
  • verificationCode: a string, the code sent to the user as a code or within a link.

In addition, one of the two following options must be sent:

  • phoneNumber: a string containing the user's phone number, to which the code or link was delivered via SMS
  • email: a string containing the user's email, to which the code or link was delivered via email

Note that in order to use passwordlessVerify, the options redirectUriand responseType: 'token'must be specified when first initializing WebAuth.

    connection: 'email',
    email: '',
    verificationCode: '389945'
  }, function (err,res) {
    // handle errors or continue

Extract the authResult and get user info

After authentication occurs, the parseHash method parses a URL hash fragment to extract the result of an Auth0 authentication response.

RS256 Requirement

This method requires that your tokens are signed with RS256 rather than HS256. For more information about this, check the Auth0.js v8 Migration Guide.

The contents of the authResult object returned by parseHash depend upon which authentication parameteres were used. It can include:

  • accessToken - an access token for the API, specified by the audience
  • expiresIn - a string containing the expiration time (in seconds) of the accessToken
  • idToken - an ID Token JWT containing user profile information
auth0.parseHash(window.location.hash, function(err, authResult) {
  if (err) {
    return console.log(err);

  auth0.client.userInfo(authResult.accessToken, function(err, user) {
    // Now you have the user's information

As shown above, the client.userInfo method can be called passing the returned authResult.accessToken. It will make a request to the /userinfo endpoint and return the user object, which contains the user's information, similar to the below example.

    "email_verified": "false",
    "email": "",
    "updated_at": "2017-02-07T20:50:33.563Z",
    "name": "",
    "picture": "",
    "user_id": "auth0|123456789012345678901234",
    "nickname": "tester9",
    "identities": [
            "user_id": "123456789012345678901234",
            "provider": "auth0",
            "connection": "Username-Password-Authentication",
            "isSocial": "false"
    "created_at": "2017-01-20T20:06:05.008Z",
    "sub": "auth0|123456789012345678901234"

You can now do something else with this information as your application needs, such as acquire the user's entire set of profile information with the Management API, as described below.

Using nonce

By default, auth0.js will generate a random nonce when you call auth0.authorize, store it in local storage, and pull it out in auth0.parseHash. The default behavior should work in most cases, but some use cases may require a developer to control the nonce. If you want to use a developer generated nonce, then you must provide it as an option to both auth0.authorize and auth0.parseHash.

  auth0.authorize({nonce: '1234'});
  auth0.parseHash({nonce:'1234'}, callback);


To log out a user, use the logout method. This accepts an options object, which can include a client_id, and a returnTo URL. If you want to navigate the user to a specific URL after the logout, set that URL at the returnTo parameter.

returnTo parameter

Note that if the client_id parameter is included, the returnTo URL that is provided must be listed in the Client's Allowed Logout URLs in the Auth0 dashboard. However, if the client_id parameter is not included, the returnTo URL must be listed in the Allowed Logout URLs at the account level in the Auth0 dashboard.

  returnTo: 'some url here',
  client_id: 'some client ID here'

Sign up

The signup method accepts an options object that contains parameters for your signup. Note that signups should be for database connections. Here is an example of the signup method and some sample code for a form.

<h2>Signup Database Connection</h2> 
<input class="signup-email" /> 
<input type="password" class="signup-password" /> 
<input type="button" class="signup-db" value="Signup!" /> 
<script type="text/javascript"> 
    $('.signup-db').click(function (e) { 
            connection: 'Username-Password-Authentication', 
            email: $('.signup-email').val(), 
            password: $('.signup-password').val()
        }, function (err) { 
            if (err) return alert('Something went wrong: ' + err.message); 
            return alert('success signup without login!') 

Using renewAuth to acquire new tokens

The renewAuth method allows you to acquire a new token from Auth0 for a user who is already authenticated against the hosted login page for your domain.

  audience: '',
  scope: 'read:something write:otherthing',
  redirectUri: '',
  usePostMessage: true
}, function (err, authResult) {


This will use postMessage to comunicate between the silent callback and the SPA. When false, the SDK will attempt to parse the URL hash, should ignore the URL hash, and no extra behaviour is needed.

The actual redirect to /authorize happens inside an iframe, so it will not reload your application or redirect away from it. However, it is strongly recommended to have a dedicated callback page for silent authentication in order to avoid the delay of loading your entire application again inside an iframe.

This callback page should only parse the URL hash and post it to the parent document, so that your application can take action depending on the outcome of the silent authentication attempt. The callback page should be something like the following one. It will parse the URL hash and post it to the parent document:

<!DOCTYPE html>
    <script src=""></script>
    <script type="text/javascript">
      var webAuth = new auth0.WebAuth({
        domain: 'YOUR_AUTH0_DOMAIN',
        clientID: '...'
      var result = webAuth.parseHash(window.location.hash, function(err, data) {
        parent.postMessage(err || data, "");

Remember to add the URL of the silent authentication callback page that you create to the Allowed Callback URLs list of your Auth0 client in the Auth0 Dashboard under your client's Settings.

Password reset requests

If attempting to set up a password reset functionality, you'll use the changePassword method and pass in an "options" object, with a "connection" parameter and an "email" parameter.

  $('.change_password').click(function () {
      connection: 'db-conn',
      email:   ''
    }, function (err, resp) {

The user will then receive an email which will contain a link that they can follow to reset their password.

User management

The Management API provides functionality that allows you to link and unlink separate user accounts from different providers, tying them to a single profile (Read more about Linking Accounts with Auth0). It also allows you to update user metadata.

To get started, create a new auth0.Management instance by passing it the account's Auth0 domain, and the token for the primary identity. In the case of linking users, this primary identity is the user profile that you want to "keep" the data for, and which you plan to link other identities to.

var auth0Manage = new auth0.Management({
  domain: 'YOUR_AUTH0_DOMAIN',

Getting the user profile

In order to get the user profile data, use the getUser() method, with the userId and a callback as parameters. The method returns the user profile. Note that the userID required here will be the part after the delimiter if using the user_id fetched from the client.userInfo method.

auth0Manage.getUser(userId, cb);

Updating the user profile

When updating user metadata, you will need to first create a userMetadata object, and then call the patchUserMetadata method, passing it the user id and the userMetadata object you created. The values in this object will overwrite existing values with the same key, or add new ones for those that don't yet exist in the user metadata. Visit the User Metadata documentation for more details on user metadata.

auth0Manage.patchUserMetadata(userId, userMetadata, cb);

Linking users

Linking user accounts will allow a user to authenticate from any of their accounts and no matter which one they use, still pull up the same profile upon login. Auth0 treats all of these accounts as separate profiles by default, so if you wish a user's accounts to be linked, this is the way to go.

The linkUser method accepts two parameters, the primary user id and the secondary user token (the token obtained after login with this identity). The user id in question is the unique identifier for this user account. If the id is in the format facebook|1234567890, the id required is the portion after the delimiting pipe. Visit the Linking Accounts documentation for more details on linking accounts.

auth0Manage.linkUser(userId, secondaryUserToken, cb);

Linking - Metadata

Note that when accounts are linked, the secondary account's metadata is not merged with the primary account's metadata, and if they are ever unlinked, the secondary account will likewise not retain the primary account's metadata when it becomes separate again.