How to Represent Multiple APIs Using a Single Auth0 API

To simplify your authentication process, you can create a single API using the Auth0 Dashboard to represent all of your existing APIs. Doing this allows you to implement just one authentication flow. You can then control access to the individual APIs by assigning the appropriate scopes.

This article shows you how to use and represent multiple APIs as a single Resource Server in Auth0 using a sample application you can download if you would like to follow along as you read. Before you set up the sample on your local environment, please make sure you set up your application in Auth0.

The Sample Application

The sample application contains:

  • 1 Single Page Application (SPA);
  • 2 APIs (called contacts and calendar).

We will represent the two APIs using just one Auth0 API called Organizer Service. We will then create two namespaced scopes to demonstrate how you can use the Implicit Grant to access the calendar and contacts APIs from the SPA. The SPA also uses Lock to implement the signin screen.

Please see the README for additional information on setting up the sample on your local environment.

The Auth0 Application

If you don't already have an Auth0 Application (of type Single Page Web Applications) with the OIDC Conformant flag enabled, you'll need to create one. This represents your application.

  1. In the Auth0 Dashboard, click on Applications in the left-hand navigation bar. Click Create Application.
  2. The Create Application window will open, allowing you to enter the name of your new Application. Choose Single Page Web Applications as the Application Type. When done, click on Create to proceed.
  3. Navigate to the Auth0 Application Settings page. Add http://localhost:3000 and http://localhost:3000/callback.html to the Allowed Callback URLs field of your Auth0 Application Settings.
  4. Scroll to the bottom of the Settings page, where you'll find the Advanced Settings section. Under the OAuth tab, enable the OIDC Conformant Flag under the OAuth area of Advanced Settings.

Enable a Connection for Your Application

Connections are sources of users to your application, and if you don't have a sample Connection you can use with your newly-created Application, you will need to configure one. For the purposes of this sample, we'll create a simple Database Connection that asks only for the user's email address and a password.

  1. In the Auth0 Dashboard, click on Connections > Database in the left-hand navigation bar. Click Create DB Connection.
  2. The Create DB Connection window will open. Provide a Name for your Connection, and click Create to proceed.
  3. Once your Connection is ready, click over to the Applications tab, and enable the Connection for your Application.

Create a Test User

If you're working with a newly-created Connection, you won't have any users associated with the Connection. Before you can test your sample's login process, you'll need to create and associate a user with your Connection.

  1. In the Auth0 Dashboard, click on Users in the left-hand navigation bar. Click Create User.
  2. Provide the requested information about the new user (email address and password), and select your newly-created Connection.
  3. Click Save to proceed.

Create the Auth0 API

Log in to your Auth0 Dashboard, and navigate to the APIs section.

For detailed information on working with APIs in the Dashboard, refer to APIs.

Click Create API.

You will be prompted to provide a name and identifier, as well as choose the signing algorithm, for your new API.

For the purposes of this article, we'll call our API Organizer Service and set its unique identifier to organize. By default, the signing algorithm for the tokens this API issues is RS256, which we will leave as is.

Once you've provided the required details, click Create to proceed.

Configure the Auth0 API

After Auth0 creates your API, you'll be directed to its Quick Start page. At this point, you'll need to create the appropriate Scopes, which you can do via the Scopes page.

Scopes allow you to define the API data accessible to your applications. You'll need one scope for each API represented and action. For example, if you want to read and delete from an API called samples, you'll need to create the following scopes:

  • read:samples
  • delete:samples

For our sample application, we'll add two scopes:

  • read:calendar;
  • read:contacts.

You can think of each one as a microservice.

Add these two scopes to your API and Save your changes.

Grant Access to the Auth0 API

You are now ready to provide access to your APIs by granting Access Tokens to the Auth0 API. By including specific scopes, you can control an application to some or all of the APIs represented by the Auth0 API.

Authorization Flows

The rest of this article covers use of the Implicit Grant to reflect the sample. You can, however, use whichever flow best suits your needs.

For a full list of available Authorization flows, see API Authorization.

The app initiates the flow and redirects the browser to Auth0 (specifically to the /authorize endpoint), so the user can authenticate.


For additional information on the call's parameters, refer to the docs on executing an implementing the Implicit Grant.

The SPA executes this call whenever the user clicks Login.

SPA Home before Login

Lock handles the login process.

SPA Login

Next, Auth0 authenticates the user. If this is the first time the user goes through this flow, they will be asked to consent to the scopes that are given to the Application. In this case, the user's asked to consent to the app reading their contacts and calendar.

Consent Screen

If the user consents, Auth0 continues the authentication process, and upon completion, redirects them back to the app with an Access Token in the hash fragment of the URI. The app can now extract the tokens from the hash fragment. In a Single Page Application (SPA) this is done using JavaScript.

function getParameterByName(name) {
  var match = RegExp('[#&]' + name + '=([^&]*)').exec(window.location.hash);
  return match && decodeURIComponent(match[1].replace(/\+/g, ' '));

function getAccessToken() {
  return getParameterByName('access_token');

The app can then use the Access Token to call the API on behalf of the user.

After logging in, you can see buttons that allow you to call either of your APIs.

SPA Home after Login

Polling checkSession() to attain SSO or SLO

In some multi-application scenarios, where Single Log Out is desired (a user logging out of one application needs to be logged out of other applications), an application can be set up to periodically poll Auth0 using checkSession() to see if a session exists. If the session does not exist, you can then log the user out of the application. The same polling method can be used to implement silent authentication for a Single Sign On scenario.

The poll interval between checks to checkSession() should be at least 15 minutes between calls to avoid any issues in the future with rate limiting of this call.