gRPC-style error codes returned by the Enterprise Data Export API v1
Questions or issues? Contact us at api-support@manus.ai.Errors follow the standard gRPC convention. The response body contains a code and a message:
{ "code": "INVALID_ARGUMENT", "message": "either user_id or email is required"}
Code
Description
INVALID_ARGUMENT
Missing or invalid request parameters.
NOT_FOUND
The requested resource does not exist (e.g., an export task UID, user, or project).
PERMISSION_DENIED
The target resource does not belong to your enterprise, or the API key lacks permissions for this operation.
FAILED_PRECONDITION
The resource is not in a valid state for the requested operation (e.g., an export is not yet completed, or its archive has been purged after the retention window).
INTERNAL
Internal server error. Retry with backoff and contact support if it persists.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.