Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

POST /lives/`{live_id}`/finish

Ends the broadcast of a live.

📘
Authorization
Requires a valid Panda API token sent in the Authorization header (no Bearer prefix).

⚠️
The status does not go straight to finished: it passes through finishing. If you show the state of the live on screen, you need to handle that intermediate status. The endpoint accepts a live in online and also in finishing, so you can repeat the call without getting an error.

HTTP Method & Path

POST /lives/{live_id}/finish

Base URL: https://api-v2.pandavideo.com.br

Authentication Requirements

Security Scheme	Header	Note
API Key	`Authorization`	Panda API token (without Bearer prefix)

Parameters

Name	In	Type	Required	Description
`Authorization`	header	string	Yes	Panda API token (without Bearer prefix)

Path Parameters

Field	Type	Required	Description
`live_id`	string (uuid)	Yes	ID of the live to finish. You get it when creating the live, or from List lives.

Request Body

None.

Response

Success Response (200)

{ "status": true }

Status after finishing

Status	When
`finishing`	Right after the call — the end was requested and is being finalized.
`finished`	The broadcast has ended.
`finished_imported`	The recording became a video. Only when the live was created with `save_vod`.

📘
No recording, no video. A live created with save_vod: false leaves no recording, so it never reaches finished_imported and there is nothing to recover afterwards.

Error Responses

// the live is not online
{ "errCode": "BadRequest", "errMsg": "live needs to be online" }

401 Unauthorized — missing or invalid API token.
404 Not Found — live not found.

Example Usage

cURL

curl -X POST "https://api-v2.pandavideo.com.br/lives/{live_id}/finish" \
  -H "Authorization: {api_key}"

Finish live

POST /lives/`{live_id}`/finish

Authorization

The status does not go straight to `finished`: it passes through `finishing`. If you show the state of the live on screen, you need to handle that intermediate status. The endpoint accepts a live in `online` and also in `finishing`, so you can repeat the call without getting an error.

HTTP Method & Path

Authentication Requirements

Parameters

Path Parameters

Request Body

Response

Success Response (200)

Status after finishing

No recording, no video. A live created with `save_vod: false` leaves no recording, so it never reaches `finished_imported` and there is nothing to recover afterwards.

Error Responses

Example Usage

cURL

POST /lives/{live_id}/finish

Authorization

The status does not go straight to finished: it passes through finishing. If you show the state of the live on screen, you need to handle that intermediate status. The endpoint accepts a live in online and also in finishing, so you can repeat the call without getting an error.

HTTP Method & Path

Authentication Requirements

Parameters

Path Parameters

Request Body

Response

Success Response (200)

Status after finishing

No recording, no video. A live created with save_vod: false leaves no recording, so it never reaches finished_imported and there is nothing to recover afterwards.

Error Responses

Example Usage

cURL

200200

400400

POST /lives/`{live_id}`/finish

The status does not go straight to `finished`: it passes through `finishing`. If you show the state of the live on screen, you need to handle that intermediate status. The endpoint accepts a live in `online` and also in `finishing`, so you can repeat the call without getting an error.

No recording, no video. A live created with `save_vod: false` leaves no recording, so it never reaches `finished_imported` and there is nothing to recover afterwards.