Database Migration Service provides a REST API for administering your connection profiles and migration jobs programmatically. The REST API is defined by resources associated with creating and managing connection profiles and migration jobs. For details about all resources
and their methods, see the
Database Migration Service API Reference.
When you send requests directly to the Database Migration Service REST API, you must create the
correct form of the request, authorize the request as an authenticated user, and
process any responses returned. Many of the tasks in this documentation provide
API examples using cURL.
For more examples of using the APIs, see the page for the request in the
Database Migration Service API Reference. Each page has
examples calling the API in several programming languages, as well as a
request-specific Explorer to help you see what goes into a well-formed request
and what to expect in the response.
You're also using the Database Migration Service API, indirectly, when you use any of the
following ways of administering instances:
Google Cloud CLI: A command-line interface (CLI) that you can use to work with your instances.
The advantage of using these methods, especially the
Google Cloud console, is that they can greatly simplify administering your
connection profiles and migration jobs (depending on your use case). If you're just starting out with
Database Migration Service, then we recommend that you start with one of these tools first
before working with the REST API directly.
Enable the API
To use the Database Migration Service API, you need to enable it:
Enter the following to display the project IDs for your Google Cloud
projects:
gcloudprojectslist
Set your default project:
gcloudconfigsetprojectYOUR_PROJECT_ID
Enable the Cloud SQL Admin API:
gcloudservicesenabledatamigration.googleapis.com
Permissions
You must have the required permissions to use the Database Migration Service API. These permissions include:
Database Migration Admin: With this permission, a user gains access to all resources of Database Migration Service used to manage connection profiles and migration jobs.
Database Migration Viewer: With this permission, a user has read-only access to connection profiles and migration jobs in Database Migration Service.
Cloud SQL Admin: With this permission, a user can create and manage connection profiles and migration jobs for Cloud SQL in Database Migration Service.
Google Cloud offers Identity and Access Management (IAM), which lets you give more granular access to specific Google Cloud resources and prevents unwanted access to other resources. You can get and set permissions for Database Migration Service using the Google Cloud console, the IAM methods of the API, or the Google Cloud CLI. For more information, see Granting, changing, and revoking access to resources.
When you use the API with cURL, you provide property values using the command
line. If you're working with sensitive values such as passwords or security
keys, providing them on the command line poses a security risk. For increased
security, you can create a file containing the JSON data for the API call, and
provide the path to the file on the command line.
To provide JSON data to your cURL API call from a file:
Create a file containing everything enclosed in single quotes for the
--data field.
Include the curly brackets, but don't include the single quotes.
At the command line, provide the path to the file, preceded by the
@ character, as the --data parameter:
--data@<path-to-file>/<filename>
For example, to create a connection profile for a Cloud SQL source database, you could create a file named request.json with the following content:
Some API calls, such as object creation, can take some time to complete. Because
the API is asynchronous, the call returns immediately, even if the operation is
still in progress. If a subsequent API call uses the newly created object, then you
must wait for the first operation to complete before proceeding.
You can use the Database Migration Service API to manage operations. This includes:
In the Discovery Service, Database Migration Service is represented as "datamigration" (for example:
https://datamigration.googleapis.com/$discovery/rest?version=v1).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eDatabase Migration Service offers a REST API for programmatically managing connection profiles and migration jobs, detailed in the Database Migration Service API Reference.\u003c/p\u003e\n"],["\u003cp\u003eWhile the REST API can be used directly with tools like cURL, users can also indirectly utilize it through the Google Cloud CLI and Google Cloud console, which simplify administration.\u003c/p\u003e\n"],["\u003cp\u003eThe API can be enabled in the Google Cloud console or via gcloud CLI commands, with various permission levels available, such as Database Migration Admin, Viewer, and Cloud SQL Admin.\u003c/p\u003e\n"],["\u003cp\u003eFor secure handling of sensitive data, the API can accept JSON data from a file, rather than directly from the command line, when using cURL.\u003c/p\u003e\n"],["\u003cp\u003eLong-running API operations are handled asynchronously, requiring users to manage them with the Database Migration Service API, allowing for checking status and deleting operations if needed.\u003c/p\u003e\n"]]],[],null,["# Use the Database Migration Service API\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/use-the-database-migration-service-api \"View this page for the MySQL version of Database Migration Service.\") \\| PostgreSQL \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/use-the-database-migration-service-api \"View this page for the PostgreSQL to AlloyDB version of Database Migration Service.\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nOverview\n--------\n\nDatabase Migration Service provides a REST API for administering your connection profiles and migration jobs programmatically. The REST API is defined by resources associated with creating and managing connection profiles and migration jobs. For details about all resources\nand their methods, see the\n[Database Migration Service API Reference](/database-migration/docs/reference/rest).\n\nWhen you send requests directly to the Database Migration Service REST API, you must create the\ncorrect form of the request, authorize the request as an authenticated user, and\nprocess any responses returned. Many of the tasks in this documentation provide\nAPI examples using [cURL](http://curl.haxx.se).\n\nFor more examples of using the APIs, see the page for the request in the\n[Database Migration Service API Reference](/database-migration/docs/reference/rest). Each page has\nexamples calling the API in several programming languages, as well as a\nrequest-specific Explorer to help you see what goes into a well-formed request\nand what to expect in the response.\n\nYou're also using the Database Migration Service API, indirectly, when you use any of the\nfollowing ways of administering instances:\n\n- [Google Cloud CLI](/sdk): A command-line interface (CLI) that you can use to work with your instances.\n\n- [Google Cloud console](https://console.cloud.google.com/): A graphical web interface.\n\nThe advantage of using these methods, especially the\nGoogle Cloud console, is that they can greatly simplify administering your\nconnection profiles and migration jobs (depending on your use case). If you're just starting out with\nDatabase Migration Service, then we recommend that you start with one of these tools first\nbefore working with the REST API directly.\n\nEnable the API\n--------------\n\nTo use the Database Migration Service API, you need to enable it: \n\n### Console\n\n1. [Enable the Database Migration Service API](https://console.cloud.google.com/apis/library/datamigration.googleapis.com).\n2. Select your project.\n3. Select **Continue**.\n\n### gcloud\n\n1. Enter the following to display the project IDs for your Google Cloud projects: \n\n ```bash\n gcloud projects list\n ```\n2. Set your default project: \n\n ```bash\n gcloud config set project YOUR_PROJECT_ID\n ```\n3. Enable the Cloud SQL Admin API: \n\n ```bash\n gcloud services enable datamigration.googleapis.com\n ```\n\nPermissions\n-----------\n\nYou must have the required permissions to use the Database Migration Service API. These permissions include:\n\n- Database Migration Admin: With this permission, a user gains access to all resources of Database Migration Service used to manage connection profiles and migration jobs.\n- Database Migration Viewer: With this permission, a user has read-only access to connection profiles and migration jobs in Database Migration Service.\n- Cloud SQL Admin: With this permission, a user can create and manage connection profiles and migration jobs for Cloud SQL in Database Migration Service.\n\nGoogle Cloud offers Identity and Access Management (IAM), which lets you give more granular access to specific Google Cloud resources and prevents unwanted access to other resources. You can get and set permissions for Database Migration Service using the Google Cloud console, the IAM methods of the API, or the Google Cloud CLI. For more information, see [Granting, changing, and revoking access to resources](/iam/docs/granting-changing-revoking-access).\n\nAPI examples\n------------\n\nFor examples of using the Database Migration Service API with cURL, see [Manage connection profiles using the API](/database-migration/docs/postgres/api-connection-profiles) and [Manage migration jobs using the API](/database-migration/docs/postgres/api-migration-jobs).\n\nProvide JSON data from a file\n-----------------------------\n\nWhen you use the API with cURL, you provide property values using the command\nline. If you're working with sensitive values such as passwords or security\nkeys, providing them on the command line poses a security risk. For increased\nsecurity, you can create a file containing the JSON data for the API call, and\nprovide the path to the file on the command line.\n\nTo provide JSON data to your cURL API call from a file:\n\n1. Create a file containing everything enclosed in single quotes for the\n `--data` field.\n\n Include the curly brackets, but don't include the single quotes.\n2. At the command line, provide the path to the file, preceded by the\n `@` character, as the `--data` parameter:\n\n ```bash\n --data @\u003cpath-to-file\u003e/\u003cfilename\u003e\n ```\n\n \u003cbr /\u003e\n\n For example, to create a connection profile for a Cloud SQL source database, you could create a file named `request.json` with the following content: \n\n ```\n {\n \"displayName\": \"my Cloud SQL connection profile\",\n \"mysql\": {\n \"host\": \"10.11.12.13\",\n \"port\": 5432,\n \"username\": \"myusername\",\n \"password\": \"mypassword\"\n }\n }\n ```\n\n Then, you would use the following cURL command at the command line: \n\n ```bash\n curl --header \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n --header 'Content-Type: application/json' \\\n --data @./request.json \\\n -X POST \\\n https://datamigration.googleapis.com/v1/projects/myProject/locations/myLocation/connectionProfiles?connectionProfileId=myCloudSQLconnectionprofile\n ```\n\nWork with long-running API calls\n--------------------------------\n\nSome API calls, such as object creation, can take some time to complete. Because\nthe API is asynchronous, the call returns immediately, even if the operation is\nstill in progress. If a subsequent API call uses the newly created object, then you\nmust wait for the first operation to complete before proceeding.\n\nYou can use the Database Migration Service API to [manage operations](/sdk/gcloud/reference/database-migration/operations). This includes:\n\n- [Showing details about an operation](/sdk/gcloud/reference/database-migration/operations/describe)\n- [Listing operations for a region](/sdk/gcloud/reference/database-migration/operations/list)\n- [Deleting an operation](/sdk/gcloud/reference/database-migration/operations/delete)\n\nDatabase Migration Service and Google APIs Discovery Service\n------------------------------------------------------------\n\n[Google APIs Discovery Service](/discovery) is a service that you can use to\ndiscover Google APIs. For example, when you use the [Google APIs Explorer](/apis-explorer) tool, you're using the Discovery Service.\n\nIn the Discovery Service, Database Migration Service is represented as \"datamigration\" (for example:\nhttps://**datamigration**.googleapis.com/$discovery/rest?version=v1)."]]