1. Types
2. content
3. library
4. item

## content library item: transfer endpoint

The `transfer_endpoint` structure encapsulates a URI along with extra information about it.

### Representations:

- JSON
- XML

{
"ssl_certificate_thumbprint": "string",
"uri": "http://myurl.com"
}
<?xml version="1.0" ?>
<ns0:TransferEndpoint xmlns:ns0="http://vmware.com/content/library/item" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ssl_certificate_thumbprint>string</ssl_certificate_thumbprint>
<uri>http://myurl.com</uri>
</ns0:TransferEndpoint>

#### Attributes:

Name | Type | Description
--- | --- | ---
Required
uri | URI | Transfer endpoint URI. The supported URI schemes are: `http`, `https`, `file`, and `ds`. An endpoint URI with the `ds` scheme specifies the location of the file on the datastore. The format of the datastore URI is: ds:///vmfs/volumes/uuid/path Some examples of valid file URI formats are: file:///path file:///C:/path file://unc-server/path When the transfer endpoint is a file or datastore location, the server can import the file directly from the storage backing without the overhead of streaming over HTTP.
Optional
ssl_certificate_thumbprint | string | Thumbprint of the expected SSL certificate for this endpoint. Only used for HTTPS connections. The thumbprint is the SHA-1 hash of the DER encoding of the remote endpoint's SSL certificate. If set, the remote endpoint's SSL certificate is only accepted if it matches this thumbprint, and no other certificate validation is performed. Optional. If not specified, standard certificate validation is performed.