> ## Documentation Index
> Fetch the complete documentation index at: https://docs.manus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Compliance-focused data exports via the v1 RPC API

<sup>Questions or issues? Contact us at [api-support@manus.ai](mailto:api-support@manus.ai).</sup>

# Enterprise Data Export

Lets enterprise administrators export user data for **compliance** purposes, including legal hold requests and internal audits. Every operation is a `POST` to `/dataexport.v1.EnterpriseDataExportService/<Method>`.

<Card title="Quickstart" icon="rocket" href="/enterprise/v1/data-export-quickstart">
  Run a complete export end-to-end with five curl calls.
</Card>

## Endpoints

| Operation                  | Page                                                                          |
| -------------------------- | ----------------------------------------------------------------------------- |
| Preview a user's tasks     | [enterprise.task.list](/enterprise/v1/enterprise.task.list)                   |
| Create a compliance export | [enterprise.export.create](/enterprise/v1/enterprise.export.create)           |
| Get an export's status     | [enterprise.export.detail](/enterprise/v1/enterprise.export.detail)           |
| List a user's past exports | [enterprise.export.list](/enterprise/v1/enterprise.export.list)               |
| Mint a download URL        | [enterprise.export.downloadUrl](/enterprise/v1/enterprise.export.downloadUrl) |

## Export lifecycle

```
PENDING → PROCESSING → COMPLETED
                   ↘
                     FAILED / CANCELLED
```

[`CreateExport`](/enterprise/v1/enterprise.export.create) returns immediately with `EXPORT_STATUS_PENDING`. The actual export runs asynchronously. Poll [`GetExport`](/enterprise/v1/enterprise.export.detail) until status is `EXPORT_STATUS_COMPLETED`, then read `record.file_url` (or call [`GetDownloadURL`](/enterprise/v1/enterprise.export.downloadUrl) for a fresh URL once `record.url_expires_at` has passed).

## Export file structure

The exported ZIP archive contains JSON files organized by data type:

```
export_xxx.zip
├── user.json                    # User profile (includes user ID, name, email)
├── platform_user.json           # Platform account bindings
├── user_client_config.json      # Client configurations
├── user_personalization.json    # Personalization settings
├── project.json                 # Project information
├── session_info.json            # Session data with events
├── session_file_info.json       # File metadata
├── skill.json                   # Skill metadata
├── user_knowledge.json          # Knowledge base
├── notifications.json           # Notifications
├── team.json                    # Team information
├── team_user_relation.json      # Team member relationships
├── skills/                      # Skill archive files
│   └── skill_uid/
│       └── MySkill.zip
└── files/                       # Session files
    └── session_uid/
        └── document.pdf
```

## Operational notes

1. **User scope.** You can retrieve data for any user who is currently or was previously a member of your enterprise, including deleted accounts.
2. **Async processing.** `CreateExport` returns immediately; the actual export runs in the background.
3. **File retention.** Export files are retained for **30 days** by default.
4. **Download URL validity.** Pre-signed URLs expire after **10 minutes**. Mint a new one as needed.
5. **Concurrency.** Recommended to keep at most one in-flight export per user.
6. **Audit logging.** All export operations are logged for compliance review.