Tusd protocol for uploading to our servers
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Headers
| Headers params | Type | Description |
|---|---|---|
| Tus-Resumable | String | The Tus-Resumable header MUST be included in every request and response with value 1.0.0 |
| Upload-Length | Number | The Upload-Length header indicates the size of the entire upload in bytes. |
| Content-Type | String | application/offset+octet-stream |
| Upload-Metadata | String | The Upload-Metadata request and response header MUST consist of one or more comma-separated key-value pairs. The key and value MUST be separated by a space. The key MUST NOT contain spaces and commas and MUST NOT be empty. The key SHOULD be ASCII encoded and the value MUST be Base64 encoded. All keys MUST be unique. In these cases, the space, which would normally separate the key and the value, MAY be left out. Possible values:
|
Usage example available in our github
Uploader URLUploads go to the upload server, not to
api-v2.pandavideo.com.br. Send them to the global endpointhttps://uploader.pandavideo.com/files/— there is no need to pick a regional server. The regional hosts returned by List Uploader Servers (e.g.uploader-us01.pandavideo.com.br) are legacy; new integrations should use the global endpoint.Full examples in Node.js, Python and cURL: Upload a video (TUS).
Please check tus protocol documentation.