Control & Monitor File Transfers

Control active transfers (cancel, pause, resume), retry failures, replay transfers, and monitor progress.

Transfers are created through automation (see Automate File Transfers). The public API endpoint for creating one-time transfers (POST /api/transfers/manual) has been removed. In the examples below, monitorId identifies the created transfer and can be retrieved through GET /api/transfers (active transfer list).

Browse Transfer Paths#

POST /api/devices/{deviceId}/files/search — Browse device paths

Check file and folder paths on the source device. Each returned item includes a hash that can be passed to automation source items and related operations.

curl -X POST https://app.innorix.com/api/devices/dev_a1/files/search \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>" \
  -H "Content-Type: application/json" \
  -d '{ "path": "/data/export", "onlyFolder": false }'

Search results are paginated. If the POST response returns a nextCursor with the first batch, use the GET request below to retrieve subsequent batches while hasMore is true. Reusing the same cursor returns the same batch (idempotent), while requesting the nextCursor acknowledges the previous batch.

GET /api/devices/{deviceId}/files/search — Retrieve the next search batch

curl "https://app.innorix.com/api/devices/dev_a1/files/search?cursor=<NEXT_CURSOR>" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>"

Transfer Control#

Each control action is now a POST to a transfer-specific subresource (no request body).

curl -X POST https://app.innorix.com/api/transfers/mon_7788/pause \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>"

Bulk Cancel · Retry Failures · Replay#

Cancel multiple transfers — POST /api/transfers/bulk-cancel

curl -X POST https://app.innorix.com/api/transfers/bulk-cancel \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>" \
  -H "Content-Type: application/json" \
  -d '{ "monitorIds": ["mon_123", "mon_456"] }'

Retry failed files — POST /api/transfers/{monitorId}/retry

The transfer is identified by the monitorId in the path, and the request body lists the files to retry.

curl -X POST https://app.innorix.com/api/transfers/mon_7788/retry \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>" \
  -H "Content-Type: application/json" \
  -d '{
    "filesRetry": [
      { "filePath": "C:/Users/MY PC/Downloads/test/file.txt", "isDir": false }
    ]
  }'

Replay previous transfer — POST /api/transfers/{monitorId}/replay

Run the previous transfer again with the same configuration (no request body). If needed, first retrieve the replay configuration through GET /api/transfers/{monitorId}/replay-data.

curl -X POST https://app.innorix.com/api/transfers/mon_7788/replay \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>"

Retrieve transfer file list — GET /api/transfers/{monitorId}/files

curl "https://app.innorix.com/api/transfers/mon_7788/files?page=1&size=50" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "x-workspace-id: <WORKSPACE_ID>"