Manus API Integration Guide

Use this skill when building or troubleshooting integrations that call the Manus API, automate Manus agents, retrieve generated results, manage projects/files/webhooks/connectors/agents/usage, request structured JSON outputs, publish websites created by Manus tasks, or implement OAuth2 authorization for third-party apps.

This file is the routing and decision guide. Keep implementation details in the live official documentation under https://open.manus.ai/docs/. When a user asks for exact request bodies, response schemas, validation rules, rate limits, or endpoint-specific edge cases, open the relevant API v2 page instead of relying on this overview.

Version policy. Use API v2 for all new work. Use the API v1 documentation only when the user is maintaining an existing v1 integration, because v1 is deprecated.

Base URL and authentication. Send requests to https://api.manus.ai. Use x-manus-api-key: <key> for your own integrations and scripts, or Authorization: Bearer <access_token> for an Open App acting on behalf of a user. Successful responses use an ok: true envelope; failures use ok: false with error.code, error.message, and request_id. Standard OAuth tokens are scoped and cannot access full-access-only endpoints. Tokens issued to a Trusted team client or Trusted public client bypass scope restrictions. Open the endpoint page to confirm its supported authentication methods.

1. Documentation Routing

Prefer reading the smallest relevant document before answering detailed implementation questions. For endpoint-specific parameters, open https://open.manus.ai/docs/v2/<endpoint>; for the full schema, inspect the API v2 OpenAPI specification.