---
title: Transfer from the command line
label: Command line
description: Send, receive, resume, and manage links with the VOTPort client.
layout: docs
order: 140
---

Use the client release supplied for your deployment. [Downloads](/downloads/) explains how to obtain the appropriate build. Run `votport help` to see the commands supported by your installed version.

## Send and receive

A request link accepts files; a delivery link provides files to download. Keep links private: possession of a link grants the access its owner configured.

```sh
votport send 'https://transfer.example/r/REQUEST_TOKEN' './Project folder'
votport receive 'https://transfer.example/s/DELIVERY_TOKEN' './Downloads'
```

Replace the example links with the links you received. Sending a folder preserves its name. Receiving verifies files against their announced roots. The client uses native transfer when the deployment offers it and the connection succeeds, with HTTP fallback where supported.

For a password-protected link, add `--password` followed by the password. Command arguments may be recorded in shell history or visible to local process inspection; use the browser when those would expose a sensitive password.

```sh
votport inspect 'https://transfer.example/r/REQUEST_TOKEN'
votport status
votport resume TRANSFER_ID
```

`inspect` reports the link type, limits, and available information. `status` lists journaled transfers; use the transfer ID with `resume` after an interruption. Keep the original source files available and unchanged when resuming a send.

## Sign in to your port

Sign in to manage requests, deliveries, and the library. The sign-in command reads its password from standard input when `--password` is omitted.

```sh
votport signin 'https://transfer.example'
votport port
votport signout
```

Use credentials approved by your administrator. Administrative capabilities still depend on your account's permissions.

## Manage requests and deliveries

```sh
votport requests
votport issue-request 'Camera originals' --expires-days 7 --max-bytes 100000000000
votport close-request REQUEST_ID

votport library
votport upload './Final cut.mov' --into 'Deliverables'
votport deliveries
votport issue-delivery 'Review copy' 'Deliverables/Final cut.mov' --expires-days 7 --max-downloads 3
votport revoke-delivery DELIVERY_ID
```

`upload` copies local files into the port's library. `issue-delivery` selects paths from that library. Check the resulting link and limits before sharing it. Closing a request stops new submissions; revoking a delivery stops further access through that link.

## Watch a folder

```sh
votport watch add './Exports' 'https://transfer.example/r/REQUEST_TOKEN'
votport watch list
votport watch run
votport watch remove WATCH_ID
```

Keep `watch run` running for the configured watches to operate. The destination request must remain valid and have sufficient quota. Test the workflow with a small export before using it for unattended work. Successfully sent drops move into the watched directory’s `shipped` subfolder. The [automation guide](/docs/using/automation/) explains settling, failed drops, and the separate server-side sharing API.

## Automation

Commands that support `--json` emit machine-readable results or progress events. Check the process exit code as well as the output: successful commands exit with zero; failures print an error and exit with a nonzero status. Preserve transfer IDs so a failed job can resume instead of starting another transfer blindly.

## Use scoped agent access

Use `votport agent` for integrations that need access to a project folder without an operator session. Set `VOTPORT_URL` and `VOTPORT_AUTOMATION_TOKEN` in the calling process’s private environment, then inspect its access:

```sh
votport agent session
votport agent files --limit 50
votport agent share 'Projects/Film/Final' --operation-id film-final-v03 --expires-days 7
votport agent recover film-final-v03
```

All `agent` commands return JSON without a `--json` flag. Persist the operation ID before creation and reuse it with identical parameters after a timeout to recover the same delivery. Commands also support delivery listing, inspection, and revocation according to the token’s permissions.

`votport mcp` exposes 15 stdio MCP tools using specification 2026-07-28. The desktop bundles name the client `votport-cli` or `votport-cli.exe`; use the installed client path rather than the server executable. See [automation setup and API reference](/docs/using/automation/) for credentials, examples, pagination, and error handling.

## Project jobs and recipient evidence

Use `votport agent projects` to discover permitted projects, `votport agent create-job delivery.json` to queue a persistent job, and `votport agent job JOB_ID` to inspect preparation and release. The [automation reference](/docs/using/automation/#queue-a-persistent-project-job) lists job commands, request fields, schedules, deadlines, and S3 imports.

After a native receive, `votport evidence list` shows local verification reports and `votport evidence retry` flushes pending submissions without downloading the files again. `votport evidence accept VERIFICATION_ID` explicitly accepts the verified package. These recipient commands use the local device identity, not the agent token. See [verification and acceptance](/docs/using/verification/#confirm-recipient-verification-and-acceptance) before advancing dependent work.