Upload a lesson video

POST /api/v1/lessons/{lessonId}/video-upload

Prepares a hosted video for one lesson, in one call: the video is created on Bunny Stream, it enters the media library as processing, and its player address is set as the lesson's video right away. You then send the file yourself, straight to the video host, with the signed credentials of the response — the file never goes through Cohorte.

Authorization

Path parameters

Request headers

Request body

Example

# 1. Open the upload — the lesson now points at the new video.
curl -X POST "$COHORTE_API_BASE_URL/api/v1/lessons/$LESSON_ID/video-upload" \
  -H "x-api-key: $COHORTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title": "Welcome", "mimeType": "video/mp4"}'

# 2. Send the file with any TUS client, using the four signed headers.
#    Metadata values are base64-encoded, as the TUS protocol requires.
curl -X POST "$UPLOAD_ENDPOINT" \
  -H "Tus-Resumable: 1.0.0" \
  -H "Upload-Length: $(wc -c < welcome.mp4 | tr -d ' ')" \
  -H "Upload-Metadata: filetype $(printf video/mp4 | base64),title $(printf Welcome | base64)" \
  -H "AuthorizationSignature: $SIGNATURE" \
  -H "AuthorizationExpire: $EXPIRES" \
  -H "VideoId: $VIDEO_ID" \
  -H "LibraryId: $LIBRARY_ID" \
  -i
# then PATCH the returned Location with the file bytes (Upload-Offset: 0).

Response

• 201 Created — the upload is open and the lesson points at the video.
• 400 Bad Request — invalid JSON, or video hosting is not configured for this platform.
• 401 Unauthorized — missing, unknown or expired key.
• 403 Forbidden — the bearer is not OWNER or ADMIN, or the lesson's program or course is archived.
• 404 Not Found — the lesson is unknown or belongs to another school. No video is created.

Response fields

Example response

{
  "success": true,
  "data": {
    "mediaId": "8c9d0e1f-2a3b-4c4d-8e5f-6a7b8c9d0e1f",
    "lessonId": "2b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e",
    "upload": {
      "endpoint": "https://video.bunnycdn.com/tusupload",
      "libraryId": "123456",
      "videoId": "0f1e2d3c-4b5a-6978-8a9b-0c1d2e3f4a5b",
      "expires": 1759312800,
      "signature": "5e3b…"
    },
    "embedUrl": "https://iframe.mediadelivery.net/embed/123456/0f1e2d3c-4b5a-6978-8a9b-0c1d2e3f4a5b"
  },
  "correlationId": "c0ffee00-1111-4222-8333-444455556666"
}

Agent recipe

1. POST /api/v1/lessons/{lessonId}/video-upload — keep upload and mediaId.
2. Send the file to upload.endpoint with a TUS client and the four signed headers, before upload.expires.
3. Poll List media with ?kind=video until the media with mediaId is ready.
4. Publish the lesson only then.

Notes

• The lesson shows the video's encoding state until it is ready. On a published lesson, members see that state — upload before publishing.
• A failed or abandoned upload leaves the lesson on an empty video until you change it with Update a lesson.
• Calling twice opens two videos: the lesson points at the second, the first stays in the library, unused, and can be deleted.
• Images and documents do not go through here: use Upload a media.

Related

• Update a lesson
• List media
• Upload a lesson resource