Skip to main content
Questions or issues? Contact us at api-support@manus.ai. The Manus API supports two authentication methods. Every request must include one of the following headers:
Some endpoints accept only API keys and OAuth tokens from a Trusted team client or Trusted public client. Other OAuth clients cannot access these endpoints. Each endpoint page notes the supported authentication methods and required OAuth scopes.

API Key

Create an API key

1

Open API settings

Go to Manus Developers settings in the Manus webapp.
2

Generate a key

Click Create API Key and give it a descriptive name (e.g. “production”, “dev-testing”). Each account can have up to 50 API keys.
3

Copy and store securely

Copy the key immediately — it will only be shown once. Store it in a secure location such as an environment variable or secrets manager.
Keep your API keys secure and never share them publicly. Each key provides full access to your Manus account. If a key is compromised, revoke it immediately from the settings page.
Rate limits apply per user (shared across all of your API keys). See Rate Limits for the per-endpoint numbers.

Use the API key

Include the key in the x-manus-api-key header with every request:

OAuth2 Bearer Token

For third-party apps that act on behalf of team users, use OAuth2 access tokens. Include the token in the Authorization header:
Standard OAuth clients are scoped. Some endpoints require a specific scope, such as create_task or manage_all_tasks, while others require no OAuth scope. Each endpoint page states its requirement. See the Open App guide for the complete setup flow, available scopes, and token lifecycle. To identify the user associated with an API key or OAuth token, call user.me. The endpoint is read-only and does not require an additional OAuth scope.
Team only: Open App creation and authorization require a Team account. Only users in the same team as the app creator can authorize the app.

Authentication errors

If the key or token is missing, the API returns:
Invalid, expired, or revoked credentials also return unauthenticated. OAuth clients must use the documented message keywords to distinguish token refresh from reauthorization. See Authentication errors.