Which API is used to migrate workbooks from test to production data sources?

The choice of the Document API for migrating workbooks from test to production data sources can be attributed to its specific functionality for handling Tableau workbooks. The Document API allows users to programmatically interact with Tableau workbook files, enabling actions such as reading, modifying, and saving those files in a structured manner.

When it comes to migrating workbooks, the Document API is particularly suited for this task because it can manipulate the XML structure within Tableau workbook files, such as changing the data source connections from test to production environments. This results in a smoother transition, as it deals directly with the contents of the workbook rather than just the metadata.

In contrast, while the REST API provides extensive capabilities for interacting with Tableau Server, such as creating, updating, and deleting resources, it is not specifically designed for the internal structure of the Tableau workbook file. The Hyper API is focused on creating and managing Hyper files, which are used for data storage and execution rather than direct workbook migration. The Webhooks API facilitates the notification of events occurring in Tableau, but it does not provide functionality for workbook manipulation or migration.

Hence, the Document API is the most appropriate choice for migrating workbooks, focusing on the necessary file interactions to successfully change data sources from one environment to another.