Give every service, partner, and customer system its own access to your API.
Everything that calls your API gets its own credential, limited to the permissions you allow.
Each service gets its own credential and only the access it needs.
Dedicated credentials for each backend service
Backend services, cron jobs, and external daemons authenticate as their own machine-to-machine apps. Each gets an isolated client credential and strictly the permissions defined by its roles, eliminating shared root keys and standing admin access.
Multiple active secrets for zero-downtime rotation
Every machine app supports multiple concurrent secrets with independent expiry dates. Deploy a new secret before revoking the old one to keep services running without maintenance windows. Revoking a compromised credential affects only that single caller.
Each machine token works for one customer only.
Run platform services across organizations without a god token
Your internal workers and sync jobs connect as a single machine app added to each customer's organization. Instead of a dangerous super-admin key, the service requests a short-lived token for one organization at a time. That token carries only the machine roles the app holds in that organization.
Dedicated credentials with strict customer boundaries
Provision dedicated machine credentials for enterprise customers who connect their own ERPs and automation pipelines. Each credential is bound to that customer's organization. Requests for any other organization are denied, and rotating or revoking the key never disrupts other customers.
Your users call your API with API keys of their own.
API keys tied to the user's permissions
Every API key carries its owner's roles. They apply across your product and in each customer's organization. Update a user's roles, and their keys follow automatically. Trade each key for a short-lived access token to call your API.
Issue keys in the Console or in your own product
Issue API keys to any user from the Logto Console. Or build a settings page with the Management API, and let users create their own. Each key can have its own expiry date.
Act for a user and stay within their permissions.
Token exchange for downstream API calls
Your service exchanges the user's token for one bound to the next API. No token passthrough. The new token keeps the same user and never exceeds that user's permissions. AI agents work the same way.
User impersonation for support and sales
Your team sees what a customer sees, without asking for their password. Your backend decides who may impersonate whom. Logto issues a short-lived token with no refresh token. The act claim names the real operator, and custom claims can carry the ticket and reason.
Read more about API keys and machine access.
How to build yours
GuideProgrammatic authentication: API key, personal access token, and OAuth client credentials flowDiscover key concepts and common use cases for API key, Personal Access Token (PAT), and Logto Machine-to-Machine (M2M) credentials.
GuideWhat is personal access token (PAT)? A more secure API tokenExplain how personal access tokens (PATs) work, when to use them, how to support API authentication in your services, and how they differ from API keys, API tokens, bearer tokens, OAuth tokens, and passwords.
Hand out API access as easily as you add a user.
Your services, your customers' systems, and your users each get their own access, limited to what you allow.