In this article, we will reemphasize the definition of the Logto Management API, explain how it works, and showcase typical scenarios to boost your productivity and unlock more use cases.
As an infrastructure service, we strive to make using our Logto Management API easier and faster. We've recently updated our guides and tutorials. In this article, we will reemphasize the definition of the Logto Management API, explain how it works, and showcase typical scenarios to boost your productivity and unlock more use cases.
The Logto Management API is a powerful set of pre-built APIs that gives developers full control to customize their implementation to suit their product needs and tech stack.
It is listed in the API resource list and cannot be deleted or modified. Everything you can do in the Logto Admin Console can also be done with the Logto Management API.
It identifier is in the pattern of https://[tenant-id].logto.app/api
It includes all permissions by default. As Logto grows, we will continue to make permissions more granular.
With the Logto Management API, you can access Logto's robust backend services, which are highly scalable and can be utilized in a multitude of scenarios. To learn about the APIs that are available, please visit Logto API references.
Our developers have implemented many additional features using our Management API. We believe that our API is highly scalable and can support a wide range of your needs. Here are a few examples of scenarios that are not possible with the Logto Admin Console but can be achieved through the Management API.
Logto currently does not provide a pre-built UI solution for user profiles. We recognize that user profiles are closely tied to business and product attributes. While we work on determining the best approach, we suggest using our APIs to create your own solution. For instance, you can utilize our interaction API, profile API, and verification code API to develop a custom solution that meets your needs. We've prepared a dedicated page User Profile for tutorials and guides.
An interesting example is that the Logto Cloud user profile feature is built using the Logto Management API.
If you're using the organization feature to build your multi-tenant app, you might need the Logto management API for tasks like org invitations and member management.
Similarly, Logto Cloud invitation and collaboration feature is built using the Logto Management API too.
To extend that case, for your SaaS product, where you have both admins and members in the tenant, the Logto management API can help you create a custom admin portal tailored to your business needs. Check out this for more detail.
The Logto Admin Console supports basic search and filtering functions. If you need more advanced options to tailor your user management service to your business needs, you can use the Logto Management API. It supports advanced search options, such as:
Check out our Advanced User Search tutorials and guides.
Logto's audit log allows you to easily monitor user activity and events. It provides a strong foundation for various user management and health check business scenarios.
By utilizing the management API, you can access real-time audit log data. This allows you to design your own schema model and dashboard using the log data obtained from Logto.
Using the Management API can easily help you import user data, especially you want to do a migration to Logto.
After you prepare the user data and set up password hashing and the user schema, set up the Management API connection and we'll call create user API to import the user data. To learn more about the migration, check out this document.
Select the M2M app type and start the creation process. After creation, you'll be directed to a module where you can assign a machine-to-machine role.
After providing a name and description, you'll see a module that asks you to assign a role. This module includes all M2M roles, roles indicated by a Logto icon means that these roles include Logto management API permissions.
Assigning M2M roles include Logto management API permissions for your M2M app.
Why does Logto allow M2M (Machine-to-Machine) communication to call the Logto Management API instead of using API keys?
Logto tackles customer identity management and strictly follows open standards like OAuth 2.0 and OpenID Connect. M2M tokens offer secure server-to-server interactions with specific scopes, providing better security than static API keys. Unlike API keys, which don't expire and pose a higher risk if compromised, M2M tokens have defined expiration times, limiting the window for potential misuse.
In Logto, we use role-based access control (RBAC) to protect and manage access to the Logto Management API. This entity diagram shows how it works.
The relationship of permissions, API resources, roles and machine-to-machine application.
M2M app makes a POST request to the token endpoint to fetch an access token by adding the following parameters using the application/x-www-form-urlencoded format in the HTTP request entity-body:
client_credentialsAnd you also need to include your M2M credentials for the token endpoint to authenticate your M2M app. This is achieved by adding a Authorization header using Basic authentication, where username is the App ID, and password is the App Secret.
You can find the App ID and App Secret from your M2M applicaiton details page:
An example of the Logto Management API access token request is:
Logto provides a built-in “Logto Management API” resource, it's a readonly resource with the all permission to access Logto Management API, you can see it from your API resource list.
The resource API indicator is in the pattern of https://{YOUR_TENANT_ID}.logto.app/api , and this will be your resource value used in the access token request body.
Before accessing Logto Management API, make sure your M2M app has been assigned with M2M roles that include the all permission from this built-in “Logto Management API” resource.
Now, compose all we have and send the request:
A successful response body would be like:
You may notice the token response has a token_type field, which it's fixed to Bearer. Thus you should put the Access Token in the Authorization field of HTTP headers with the Bearer format (Bearer YOUR_TOKEN).
Now you can access the Logto Management API by reqeusting the Logto Managemetn API endpoint https://[your-tenant-id].logto.app/api, to get all applications in Logto
Here are some related resources that delve into our previous insights and strategies for using the Logto Management API. These materials cover various aspects, including best practices, implementation tips, and use cases, to help you make the most out of the Logto Management API for your projects.