All Products
Search
Document Center

Data Management:Data Agent Personal Space Migration and OpenAPI Parameter Update

Last Updated:Mar 18, 2026

To unify the space management model of Data Agent, we are migrating data from existing personal spaces to a default personal space that has a unique space ID. This migration is transparent for console users. However, OpenAPI users must update their API parameters to ensure that session data remains correctly associated and visible in the console.

Effective date

The migration will be rolled out in phases by region, starting at 00:00:00 (Singapore time) on March 11, 2026. Specific migration schedules for each region will be announced separately.

Details

Currently, Personal Spaces in Data Agent are virtual entities without a unique workspaceId. To unify our product architecture and support future feature expansions and permission management, we are performing the following data migration:

  • Migration Destination: All personal space data (including session history and configurations) will be automatically migrated to a new, formal entity named default personal space.

  • Core Change: After the migration, the new default personal space will have a unique and permanent workspaceId.

Impacts

  • For console users:
    This migration is transparent. Your historical data and user experience will remain unchanged; no action is required.

  • For OpenAPI call users:
    This update directly affects API interactions. Once the migration is complete in your region:

    • Requirement: All operations targeting the default personal space (e.g., creating sessions, querying history) must explicitly include the workspaceId parameter in the API request.

    • Risk: API calls missing the workspaceId may still execute, but the resulting sessions or tasks will not be associated with any space. Consequently, this data will not be visible in the Data Agent console and will become orphaned.

Recommendations

We strongly recommend that Data Agent OpenAPI users take the following actions:

  • Update Application Logic: Proactively review and update your application code to include the workspaceId parameter in all relevant API calls.

  • Retrieve the Workspace ID: After the migration, you can obtain the unique workspaceId for the default personal space via:

    • The Console: Navigate to the Workspace Settings page of the default personal space.

    • The API: Call the ListWorkspaces API to fetch the WorkspaceId programmatically.

  • Stay Informed on Migration Status: Closely follow official notifications regarding the migration schedule in your region. This will ensure you can transition to the new API method as soon as the update is live.