tebarDocs
GuideDevelopersAPI ReferenceChangelog
Media

Start a chunked upload

POST
/v1/media/uploads

Send each part to PUT /v1/media/{id}/parts/{part}, then call complete.

Requires the write scope.

Authorization

bearer
headerAuthorizationBearer <token>

An API key (tb_live_...) from the dashboard, or an OAuth access token.

Header Parameters

Tebar-Profile?string

Limits an owner key to one profile (id or external_id). Unknown: 404 profile_not_found.

Request Body

application/json
  1. body
mime_type*string
Value in"image/jpeg""image/png""video/mp4""video/quicktime"
size_bytes*integer
Range0 < value <= 314572800
keep?boolean

Response Body

The part layout.

application/json
  1. response
id*string
Formatuuid
profile_id*string
Formatuuid
type*string
Value in"image""video"
mime_type*string
size_bytes*integer|null
width*|

Display width (video rotation applied).

height*integer|null
duration_ms*integer|null
frame_rate*|

Average frames per second of a video.

status*string
Value in"pending""ready""failed""expired"
public_url*string|null
poster_url*|

Videos: a small JPEG still, ready shortly after upload.

alt_text*string|null
keep*boolean

Kept in the media library. Otherwise removed 30 days after the last post using it finished, or 7 days after upload if unused.

created_at*string
Formatdate-time
part_size*integer
part_count*integer
Example Request
curl -X POST 'https://api.tebar.app/v1/media/uploads' \
  -H 'Content-Type: application/json' \
  -d '{
  "mime_type": "image/jpeg",
  "size_bytes": 1
}'
Example Response
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "profile_id": "bfcb6779-b1f9-41fc-92d7-88f8bc1d12e8",
  "type": "image",
  "mime_type": "string",
  "size_bytes": 0,
  "width": 0,
  "height": 0,
  "duration_ms": 0,
  "frame_rate": 0,
  "status": "pending",
  "public_url": "string",
  "poster_url": "string",
  "alt_text": "string",
  "keep": true,
  "created_at": "2019-08-24T14:15:22Z",
  "part_size": 0,
  "part_count": 0
}

Start a presigned upload POST

PUT the file to upload_url with exactly the Content-Type and Content-Length in upload_headers (both are signed; a mismatch gets 403 from storage), then call complete. Requires the write scope.

Upload one part PUT

part is 1-based; every part but the last is exactly part_size bytes. Requires the write scope.