manus-api

Integrate Manus agent tasks, files, webhooks, and OAuth2 Open Apps via the Manus API.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/waiyanphyo999/telegram-bot-deploy --skill manus-api-waiyanphyo999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manus-api
Source: https://github.com/waiyanphyo999/telegram-bot-deploy/tree/main/skills/manus-api
Command: npx skills add https://github.com/waiyanphyo999/telegram-bot-deploy --skill manus-api-waiyanphyo999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building integrations with the Manus API requires navigating many endpoints, authentication modes, and lifecycle rules; this Skill routes you to the correct official documentation and decision guidance so you implement tasks, projects, files, webhooks, and OAuth2 Open Apps correctly the first time. ## Core Features & Use Cases - Documentation Routing: Maps user intents (task lifecycle, structured output, website publishing, webhooks, usage) to the exact docs/v2/*.mdx endpoint file or OpenAPI spec. - Integration Decision Guidance: Covers API key vs OAuth2 authentication, task.create vs task.sendMessage flows, projects for durable instructions, webhooks vs polling, and structured output schemas. - Operational Limits Reference: Captures file upload limits (512 MB per file, 10 GB storage), attachment size caps, and OAuth scope restrictions. - Use Case: You are building a service that creates Manus tasks programmatically and needs machine-parseable JSON results delivered via signed webhooks; this Skill directs you to task.create, structured-output.mdx, and webhooks-security.mdx with the correct authentication pattern. ## Quick Start Ask how to create a Manus task with the API and receive the result through a verified webhook using an API key.

Frequently Asked Questions about manus-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Manus task with the API?

Call POST https://api.manus.ai/v2/task.create with a message.content payload and authenticate using the x-manus-api-key header. For follow-up turns, store the returned task_id and call task.sendMessage.

How do I get structured JSON output from a Manus task?

Pass structured_output_schema to task.create or task.sendMessage; extraction runs after the agent finishes. Results appear in task.listMessages as structured_output_result or in webhooks as task_stopped.task_detail.structured_output, and you should check success before trusting value.

Should I use an API key or OAuth2 for the Manus API?

Use an API key for first-party scripts and integrations, and OAuth2 Bearer tokens when building an Open App acting on behalf of team users. Standard OAuth tokens are scope-limited and cannot access agent, webhook, usage, or website endpoints.

What are the Manus API file upload limits?

file.upload accepts files up to 512 MB with 10 GB total storage per account, and exceeding either returns QuotaExceededError. Upload URLs expire in 3 minutes, files are deleted after 48 hours, and executable file types are prohibited.

Should I use webhooks or polling for Manus task results?

Polling task.listMessages works for scripts and prototypes, but production systems should use webhooks and verify signatures with the webhook public key. Implement idempotency and retries because webhook delivery can be repeated.

Can I still use Manus API v1?

API v1 is deprecated and will be removed; use v2 for all new integrations. The v1 documentation should only be consulted when maintaining an existing v1 integration.