Skip to main content
This page is for Authlete 3.0. For 2.x, see Getting Started (2.x).

1. Create an Authlete Account

To use Authlete, you need an account. Once registered, you can configure all features through the management console. Visit the Authlete website and click Free Trial in the upper-right corner.
Authlete website homepage with Free Trial button prominently displayed in the upper-right corner
Choose your preferred registration method. You can use social login (Google or GitHub) or sign up with your email address.
Signup page showing registration options: social login with Google and GitHub buttons, and an email address signup field
After verifying your social login or email address, complete the profile page by entering your first name, last name, and organization name (and Password if using email registration). Review Authlete’s Privacy Policy and Terms of Service, then click Register to agree and complete your signup.
User profile form with input fields for first name, last name, and organization name, with checkboxes to review Privacy Policy and Terms of Service, and a blue Register button

2. Create a Service

Immediately after signing up, you will be directed to the Services page. This page displays all services under your organization (which was created during the signup process). A Service represents the backend of your Authorization Server. It contains all the configurations required to operate a production-grade authorization server, including OAuth/OIDC settings, token management, and security policies. Click Create Service to add a new Authlete service to your organization.
Services page showing a list of existing services under the organization with a blue Create Service button in the upper right
  1. Select your preferred API Cluster location (e.g., US). All service data will be stored in this selected cluster. Choose the cluster based on your data residency and environment isolation requirements.
  2. Enter a Service Name (e.g., Sample Service).
  3. Click Create to complete the setup.
Create service form with dropdown menu to select API cluster location such as US, input field for service name, and a blue Create button
Now you have completed to create a new Service.

3. Create a Service Access Token

You will need a Service Access Token to authenticate your Authlete API calls. Click Service Settings for your newly created service.
Service overview page with Service Settings option displayed for the newly created service
  1. Note down the Service Identifier value (e.g., 3615784225), which is required when making requests in many Authlete APIs.
  2. Click Create Token to create a new Service Access Token.
Service settings page displaying the Service Identifier value and a blue Create Token button to generate a new Service Access Token
  1. Enter a token Name (e.g., oauth-server-token).
  2. Specify the Expiration Date.
  3. Select the appropriate Permissions (e.g., Authorization Server preset).
  4. Click Create Token.
Add a Service Access Token dialog showing Token Name field with oauth-server-token, Expiration Date field with date picker, Permission Presets section with Authorization Server option highlighted in orange, Custom Token Permissions checkboxes below, and a blue Create Token button at the bottom
The new Service Access Token will appear in the list.
  1. Click the Copy or Show icon to retrieve the token value, as it is required for most Authlete API requests. Please note that this value is only displayed once upon creation.
  2. Click Back to Service Overview to return to the main Service page.
Service Access Token list showing the newly created token with Copy and Show buttons next to it, and a Back to Service Overview link to return to the main service page
Now you are ready to test the Authlete API!

4. Call the Authlete API

Let’s make your first API request to Authlete’s /service/configuration API, which acts as the backend for the OIDC discovery endpoint, generating OpenID provider metadata so that the endpoint can return in response to requests from clients (OIDC relying parties). Below are examples using curl and the API Explorer. Please replace the placeholder values with your actual environment details.

Using curl

Run the following command in your terminal to send an HTTP GET request:
If successful, the API will return OpenID Provider Metadata similar to this:

Using API Explorer

Open the /service/configuration API reference page and click the Try it button.
API Explorer interface for the /service/configuration endpoint with Try it button ready to be clicked to test the API
  1. Choose the API Cluster Hostname.
  2. Enter the Service Access Token.
  3. Enter the Service ID.
  4. Click Send.
API Explorer form with input fields for Service ID and Service Access Token, and a blue Send button to execute the API request
The API response will be displayed in the Response section.
API response displayed in the Response section of the API Explorer showing JSON data with service configuration details including issuer, supported scopes, and response types

Next Steps

Now that your Authlete account is set up and your service is configured, it’s time to explore further:

Extra: OAuth/OIDC Processing

Let’s explore Authlete’s OAuth/OIDC protocol processing by testing a sample authorization request.

Create a Client

A Client represents an application that interacts with the Authorization Server to request tokens, or with the Resource Server to access protected resources. Clients are managed within the context of a specific Authlete Service. On the Service page, click the Create Client button at the top-right of the screen.
Service page with Create Client button located in the upper-right corner of the screen ready to be clicked
Enter a Client Name and click Create.
Create client dialog form with input field for Client Name and a blue Create button to add the new client
Once created, the client details will be displayed. Make a note of the Client ID and Client Secret if needed. In the Redirect URIs section, click Add to register your application’s redirect URIs.
Client details page showing Client ID and Client Secret values, with a Redirect URIs section and an Add button to register application redirect URIs
For example, enter https://client.example.org/cb/example.com and click Save Changes.
Redirect URI input form with example value https://client.example.org/cb/example.com and a blue Save Changes button to confirm the entry

Call “Process Authorization Request” API

Navigate to the Try /auth/authorization API tool.
  1. Choose the API Cluster Hostname.
  2. Enter the Service Access Token.
  3. Enter the Service ID.
  4. Enter the authorization request content below into the parameters field. Please note that you must replace the example client_id value (2329821874) with the one you created in the previous step.
  5. Click Send.
API Explorer showing the /auth/authorization endpoint with parameters entered
You will see the API response in the Response section.
API Explorer showing the /auth/authorization endpoint with parameters entered and the JSON response displayed in the Response section showing authorization request results