How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Logto Applications API

Application represents your registered software program or service that has been authorized to access user information and perform actions on behalf of users within the system. Currently, Logto supports four types of applications:- Traditional web- Single-page app- Native app- Machine-to-machine app.Depending on the application type, it may have different authentication flows and access to the system. See [🔗 Integrate Logto in your application](https://docs.logto.io/docs/recipes/integrate-logto/) to learn more about how to integrate Logto into your application.Role-based access control (RBAC) is supported for machine-to-machine applications. See [🔐 Role-based access control (RBAC)](https://docs.logto.io/docs/recipes/rbac/) to get started with role-based access control.

Logto Applications API is one of 39 APIs that Logto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Application. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 28 operations across 16 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version Cloud.

Requests are made against a single base URL, https://[tenant_id].logto.app/.

28 operations 16 paths 1 schemas 7 DELETE9 GET3 PATCH6 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
Cloud
Server
https://[tenant_id].logto.app/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Logto Applications API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • OAuth2 — Logto Management API is a comprehensive set of REST APIs that gives you the full control over Logto to suit your product needs and tech stack. To see the full…

Paths & Operations 28

Across 16 paths, the API surfaces 28 operations — 7 DELETE, 9 GET, 3 PATCH, 6 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Applications 28

Application represents your registered software program or service that has been authorized to access user information and perform actions on behalf of users within the system. Cu…

GET
/api/applications
Get applications
ListApplications 7 params → 200400401403
POST
/api/applications
Create an application
CreateApplication body → 200400401403422500
GET
/api/applications/{id}
Get application
GetApplication 1 param → 200400401403404
PATCH
/api/applications/{id}
Update application
UpdateApplication 1 param body → 200400401403404422500
DELETE
/api/applications/{id}
Delete application
DeleteApplication 1 param → 204400401403404422
PATCH
/api/applications/{applicationId}/custom-data
Update application custom data
UpdateApplicationCustomData 1 param body → 200400401403
GET
/api/applications/{applicationId}/roles
Get application API resource roles
ListApplicationRoles 4 params → 200400401403404422
POST
/api/applications/{applicationId}/roles
Assign API resource roles to application
AssignApplicationRoles 1 param body → 201400401403404422
PUT
/api/applications/{applicationId}/roles
Update API resource roles for application
ReplaceApplicationRoles 1 param body → 200400401403404422
DELETE
/api/applications/{applicationId}/roles/{roleId}
Remove a API resource role from application
DeleteApplicationRole 2 params → 204400401403404422
GET
/api/applications/{id}/protected-app-metadata/custom-domains
Get application custom domains.
ListApplicationProtectedAppMetadataCustomDomains 1 param → 200400401403404501
POST
/api/applications/{id}/protected-app-metadata/custom-domains
Add a custom domain to the application.
CreateApplicationProtectedAppMetadataCustomDomain 1 param body → 201400401403404409422501
DELETE
/api/applications/{id}/protected-app-metadata/custom-domains/{domain}
Remove custom domain.
DeleteApplicationProtectedAppMetadataCustomDomain 2 params → 204400401403404501
GET
/api/applications/{id}/organizations
Get application organizations
ListApplicationOrganizations 3 params → 200400401403404
DELETE
/api/applications/{id}/legacy-secret
Delete application legacy secret
DeleteApplicationLegacySecret 1 param → 200204400401403404
GET
/api/applications/{id}/secrets
Get application secrets
ListApplicationSecrets 1 param → 200400401403404
POST
/api/applications/{id}/secrets
Add application secret
CreateApplicationSecret 1 param body → 201400401403422
DELETE
/api/applications/{id}/secrets/{name}
Delete application secret
DeleteApplicationSecret 2 params → 204400401403404
PATCH
/api/applications/{id}/secrets/{name}
Update application secret
UpdateApplicationSecret 2 params body → 200204400401403404
POST
/api/applications/{applicationId}/user-consent-scopes
Assign user consent scopes to application.
CreateApplicationUserConsentScope 1 param body → 201400401403404422
GET
/api/applications/{applicationId}/user-consent-scopes
List all the user consent scopes of an application.
ListApplicationUserConsentScopes 1 param → 200400401403404
DELETE
/api/applications/{applicationId}/user-consent-scopes/{scopeType}/{scopeId}
Remove user consent scope from application.
DeleteApplicationUserConsentScope 3 params → 204400401403404
PUT
/api/applications/{applicationId}/sign-in-experience
Update application level sign-in experience
ReplaceApplicationSignInExperience 1 param body → 200201400401403404422
GET
/api/applications/{applicationId}/sign-in-experience
Get the application level sign-in experience
GetApplicationSignInExperience 1 param → 200400401403404
GET
/api/applications/{id}/users/{userId}/consent-organizations
List all the user consented organizations of a application.
ListApplicationUserConsentOrganizations 4 params → 200400401403404422
PUT
/api/applications/{id}/users/{userId}/consent-organizations
Grant a list of organization access of a user for a application.
ReplaceApplicationUserConsentOrganizations 2 params body → 204400401403404422
POST
/api/applications/{id}/users/{userId}/consent-organizations
Grant a list of organization access of a user for a application.
CreateApplicationUserConsentOrganization 2 params body → 201400401403404422
DELETE
/api/applications/{id}/users/{userId}/consent-organizations/{organizationId}
Revoke a user's access to an organization for a application.
DeleteApplicationUserConsentOrganization 3 params → 204400401403404422

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

ApplicationLegacySecret
string
The internal client secret. Note it is only used for internal validation, and the actual secrets should be retrieved from /api/applications/{id}/secrets endpoi…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

logto-applications-api-openapi.yml Raw ↑

Other APIs Logto publishes across the network.

Logto Account center API
Logto Audit logs API
Logto Authn API
Logto Captcha provider API
Logto Configs API
Logto Connector factories API
Logto Connectors API
Logto Custom phrases API
Logto Custom profile fields API
Logto Dashboard API
Logto Domains API
Logto Email templates API
Where this information came from

This is an independent, third-party profile of Logto Applications API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.