POST /2/files/move_batch_v2
move_batch
scope: files.content.write
Move multiple files or folders to different locations at once in the user's Dropbox. Note that we do not currently support case-only renaming.
This route will replace move_batch:1. The main difference is this route will return status for each entry, while move_batch:1 raises failure if any entry fails.
This route will either finish synchronously, or return a job ID and do the async move job in background. Please use move_batch/check:2 to check the job status.
Servers
- https://api.dropboxapi.com
- https://content.dropboxapi.com
- https://notify.dropboxapi.com
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
dropbox-api-path-root |
String | No | |
dropbox-api-select-user |
String | No | |
dropbox-api-select-admin |
String | No |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
autorename |
Boolean | No | |
allow_ownership_transfer |
Boolean | No | |
entries[] |
Array | No | |
entries[].from_path |
String | No | |
entries[].to_path |
String | No |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.