Skip to main content
Questions or issues? Contact us at api-support@manus.ai. Every team v2 service is generated from a protobuf definition and exposed over two interchangeable protocols:
  • REST — POST/GET /v2/<resource>.<verb> with JSON bodies / query strings. This is what the per-endpoint reference pages document.
  • Connect RPC — POST /<package>.<Service>/<Method> with the same JSON body shape (or application/connect+proto for typed Connect clients).
Both share the same authentication header (X-API-Key), the same request/response payload, and the same {ok, request_id, ...} response wrapper.

​
URL mapping

​
Enterprise Data Export (dataexport.v2.EnterpriseDataExportV2Service)

OperationRESTConnect RPC
CreateExportPOST /v2/enterprise.export.createPOST /dataexport.v2.EnterpriseDataExportV2Service/CreateExport
GetExportGET /v2/enterprise.export.detail?uid=...POST /dataexport.v2.EnterpriseDataExportV2Service/GetExport
ListExportsGET /v2/enterprise.export.list?user=...POST /dataexport.v2.EnterpriseDataExportV2Service/ListExports
GetDownloadURLGET /v2/enterprise.export.downloadUrl?uid=...POST /dataexport.v2.EnterpriseDataExportV2Service/GetDownloadURL
ListTasksGET /v2/enterprise.task.list?user=...POST /dataexport.v2.EnterpriseDataExportV2Service/ListTasks

​
Enterprise SIEM Integrations — export API (observability.v2.EnterpriseComplianceV2Service)

This service is authenticated with a KEY_TYPE_SIEM enterprise API key; other key types are rejected. The streaming (OTLP push) side is configured in the Manus console and is not part of this REST/RPC surface.
OperationRESTConnect RPC
CreateExportPOST /v2/enterprise.compliance.export.createPOST /observability.v2.EnterpriseComplianceV2Service/CreateExport
GetExportGET /v2/enterprise.compliance.export.detail?uid=...POST /observability.v2.EnterpriseComplianceV2Service/GetExport
GetDownloadURLGET /v2/enterprise.compliance.export.downloadUrl?uid=...POST /observability.v2.EnterpriseComplianceV2Service/GetDownloadURL

​
Team User Management (team.v2.TeamUserManagementApiV2Service)

OperationRESTConnect RPC
ListUsersGET /v2/team.user.listPOST /team.v2.TeamUserManagementApiV2Service/ListUsers
GetUserGET /v2/team.user.detail?email=...POST /team.v2.TeamUserManagementApiV2Service/GetUser
CreateUserPOST /v2/team.user.createPOST /team.v2.TeamUserManagementApiV2Service/CreateUser
UpdateUserPOST /v2/team.user.updatePOST /team.v2.TeamUserManagementApiV2Service/UpdateUser
DelegateProfilePOST /v2/team.user.delegatePOST /team.v2.TeamUserManagementApiV2Service/DelegateProfile
ReclaimProfilePOST /v2/team.user.reclaimPOST /team.v2.TeamUserManagementApiV2Service/ReclaimProfile
RenameProfilePOST /v2/team.user.renamePOST /team.v2.TeamUserManagementApiV2Service/RenameProfile
RemoveMemberPOST /v2/team.user.removePOST /team.v2.TeamUserManagementApiV2Service/RemoveMember

​
Shared Team Asset Governance (team.v2.TeamAssetAuditApiV2Service and team.v2.TeamAssetManageApiV2Service)

The audit and management surfaces live on two separate services so they can be authenticated with independently-rotated API keys (KEY_TYPE_TEAM_ASSET_AUDIT vs. KEY_TYPE_TEAM_ASSET_MGMT).
OperationRESTConnect RPC
ListShareableAssetsGET /v2/team.asset.listPOST /team.v2.TeamAssetAuditApiV2Service/ListShareableAssets
UpdateAssetShareScopePOST /v2/team.asset.update_scopePOST /team.v2.TeamAssetManageApiV2Service/UpdateAssetShareScope

​
When to choose which

  • Use REST for ad-hoc curl, third-party HTTP clients, no-code platforms, and the auto-rendered “Try it” panel on each endpoint page.
  • Use Connect RPC for typed clients (Go, TypeScript, Python with generated stubs) where you want compile-time guarantees on request and response shapes. Connect supports the same wire format over HTTP+JSON, so any plain HTTP client also works.
The body shape is identical either way. GET REST endpoints use query parameters; the equivalent Connect call moves those same fields into a JSON body.

​
Connect RPC examples

Same operation (GetExport) called three ways: 
buf curl \
  --schema buf.build/manus/dataexport \
  --header 'X-API-Key: <your-api-key>' \
  --data '{"uid":"5YX76pz7Dga3yztNVw97Dh"}' \
  https://api.manus.im/dataexport.v2.EnterpriseDataExportV2Service/GetExport
The auto-rendered “Try it” panel on each endpoint page only exercises the REST surface. For Connect-specific client generation, see the Connect RPC docs.