Zynk CLI

Automation

Send and receive files from shell scripts with one-shot commands and machine-readable JSON results.

Quick start

Add --json-output when your script needs to read a command’s result.

Send one file

$ zynk --json-output send Alice ./report.pdf

Replace Alice with your recipient and ./report.pdf with your file. Each send command takes one recipient. For installation and sign-in, see Setup.

Submission and delivery

A successful send means Zynk acknowledged the request. The command does not wait for the recipient to accept or receive the files.

Receiving files

List incoming transfers first, then accept the ones you want. pending shows the last 24 hours unless you widen it with --all or --since.

List pending transfers

$ zynk --json-output pending

Accept recent pending transfers

$ zynk --json-output accept --all --save-dir ./Downloads

accept --all takes every incoming transfer that has not been accepted yet, including ones older than the 24-hour window pending shows by default. Use --from or --transfer-id when you want a narrower selection.

Record: accept → data.accepted[].id
Meaning: The receive request was sent. It is not proof that the file finished.

Record: transfer_complete with data.upload: false
Meaning: The receive finished. Its data.transfer_id identifies the transfer.

Record: accept → data.failed[]
Meaning: These selections could not be requested. Read each reason.

Record	Meaning
`accept` → `data.accepted[].id`	The receive request was sent. It is not proof that the file finished.
`transfer_complete` with `data.upload: false`	The receive finished. Its `data.transfer_id` identifies the transfer.
`accept` → `data.failed[]`	These selections could not be requested. Read each reason.

Some files can finish while others fail

A nonzero exit can include completed transfers. Keep requested and completed IDs separately. If a requested ID has no completion record, check zynk --json-output list-downloads --all before retrying.