The expected format is similar as the one expected by the gSOAP-based fts-transfer-submit:
```json
{
"files":[
{
"sources":[
"gsiftp://source.host/file"
],
"destinations":[
"gsiftp://destination.host/file"
],
"metadata":"file-metadata",
"checksum":"ADLER32:1234",
"filesize":1024
},
{
"sources":[
"gsiftp://source.host/file2"
],
"destinations":[
"gsiftp://destination.host/file2"
],
"metadata":"file2-metadata",
"checksum":"ADLER32:4321",
"filesize":2048
}
]
}
```
The example above represents one single job with two transfers: one from `gsiftp://source.host/file` to `gsiftp://destination.host/file` and another from `gsiftp://source.host/file2` to `gsiftp://destination.host/file2`.
But you can do [more complex things](bulk.md) with this format!
Bulk submission
---------------
You can also check everything you can do with the [bulk format](bulk.md).
*Hint*: Try --dry-run to see what would be sent to the server
### fts-rest-whoami
This command exists for convenience. It can be used to check, as the name suggests, who are we for the server.
