---
title: "Get render status"
method: GET
path: "/renders/{renderId}"
tags: ["Renders"]
---

# Get render status

`GET /renders/{renderId}`

## Request

- Base URL: `https://api.cut.pro/api/v1`
- URL: `https://api.cut.pro/api/v1/renders/{renderId}`
- Auth: API key in header `X-Api-Key`

Returns the current status of a render job. Poll this endpoint until `status` is `completed` or `failed`.

We recommend polling every **5–10 seconds**. Use `progress` (0–100) to display a progress bar to your users.

## Path parameters

- `renderId` string, required

## Response `200`

Response for status 200

- object
  - `id` string, required: Unique render ID
  - `edit_id` string, required: Edit this render was produced from. It never expires: pass it to `POST /renders` for a fresh file, or to `POST /posts` to publish it.
  - `name` string, nullable, required: Name of the edit / clip being rendered
  - `status` 'queued' | 'active' | 'completed' | 'failed' | 'cancelled' | 'expired' | 'waiting_quality', required
  - `progress` number, required: Render progress from 0 to 100
  - `output_resolution` string, nullable, required: Output resolution, e.g. `720p` or `1080p`
  - `created_at` string, required: ISO 8601 timestamp of when the render was queued
  - `started_at` string, nullable, required: ISO 8601 timestamp of when rendering started
  - `completed_at` string, nullable, required: ISO 8601 timestamp of when the render finished

## Other responses

- `404`: Response for status 404

---

[API](https://skmtc.dev/cut/apis/cutpro-api.md) · [All operations](https://skmtc.dev/cut/apis/cutpro-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cut/apis/cutpro-api/revisions/89d0bafe529c?raw)