Overview

curl -X POST https://render-api.chillin.online/render/v1 \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d @request.json

Note: Our rendering requests are processed async. After submitting a request, you will immediately receive a response containing a render_id, which can be used to query the rendering status and results.

Prop	Type	Required	Example	Value Range	Description
compositeWidth	number	true	1920	720 - 3840	The width of the composite.
compositeHeight	number	true	1080	720 - 3840	The height of the composite.
fps	number	true	30	15 - 60	The frame rate of the composite.
projectData	object	true	-	-	The project data. Can be exported from the editor.
camera	object	false	-	-	Optional camera configuration for 3D scenes. Controls the projection mode and viewing angle.

Note: The compositeWidth and compositeHeight can differ from the width and height specified in projectData. However, the aspect ratio of compositeWidth to compositeHeight must remain consistent with the aspect ratio of projectData.width to projectData.height.

This design allows the same video project to be exported in different resolutions while maintaining the original aspect ratio.

Camera Configuration

The optional camera object controls how 3D elements are projected:

mode (string) - Projection mode: "perspective" (default) or "orthographic". Perspective provides depth-based foreshortening; orthographic preserves parallel lines.
view (string) - A preset camera view name (e.g., "front", "top", "right", "isometric"). When specified, the camera is positioned to match the preset angle.

If no camera is provided, the default perspective front view is used.

request.json

{
"compositeWidth": 1920,
"compositeHeight": 1080,
"fps": 30,
"projectData": {
  "type": "",
  "width": 1920,
  "height": 1080,
  "fill": "#000000",
  "view": [
    {
      "id": "8ecf7475-2c6c-47f9-827b-a09c7913f4c0",
      "type": "Image",
      "start": 0,
      "duration": 5,
      "trackIndex": 0,
      "x": -570.0335392757963,
      "y": -170.90659033307685,
      "blendMode": "normal",
      "anchorX": 1302,

Success Render Response

success_response.json

{
"code": 0,
"data": {
  "message": "Async render request submitted successfully",
  "render_id": 105586,
  "status": "processing"
},
"msg": "success"
}

Error Render Response

error_response.json

{
"code": 2004,
"data": {},
"msg": "invalid project data: invalid view array: view item 0: missing required field: id"
}

Response Codes

Here are the codes returned by the async rendering API:

0: Success – The async render request was submitted successfully.
2001: Parameter error – The request contains invalid or missing parameters.
2002: User not registered – The provided user ID does not exist.
2003: User is not an API member and cannot use rendering services.
2004: Invalid project data – The projectData field is not a valid JSON object.
2005: Render balance not enough – Insufficient balance to proceed with rendering.
2006: Failed to marshal project data – Could not convert project data to JSON.
2007: Failed to upload JSON data – Error occurred while uploading project data.
2008: Failed to marshal render data – Render request payload could not be serialized.
2009: Failed to send render request – Error occurred while sending the request.
2010: Missing duration field – The duration field is required but missing.
2011: Invalid duration field – The duration field is present but not in the correct format.
2012: Render service failed – The rendering service encountered an internal error.

If you encounter an error code not listed, please contact support at [email protected].

Get Render Result

After submitting an async render request, you can use the render_id to query the rendering status and result.

get-result-example.sh

curl -X POST https://render-api.chillin.online/render/result \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{"render_id": 100000}'

Request Parameters

Prop	Type	Required	Example	Value Range	Description
render_id	number	true	100000	-	The render ID returned from the initial render request.

Success Render Response

result_response.json

{
"code": 0,
"data": {
  "render": {
    "create_at": "2025-06-27T12:37:21.684337Z",
    "json_url": "https://cloud.chillin.online/project_xxx.json?verify=xxx",
    "render_id": 105549,
    "state": "success",
    "video_url": "https://cloud.chillin.online/video_xxx.mp4?verify=xxx"
  }
},
"msg": "success"
}

Render States

The state field in the response can have the following values:

pending: The render request is queued and waiting to be processed
rendering: The render is currently being processed
success: The render completed successfully and the video is ready
failed: The render failed due to an error

Delete Render Files

Use this endpoint to permanently remove the rendered video file and project JSON for a completed task.

delete-render-files.sh

curl -X POST https://render-api.chillin.online/render/delete-files \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{"render_id": 100000}'

Request Parameters

Prop	Type	Required	Example	Value Range	Description
render_id	number	true	100000	-	The render ID you want to clean up. Only renders in the success state can be deleted.

Sample Response

delete_response.json

{
"code": 0,
"data": {
  "message": "Render files deleted"
},
"msg": "success"
}

The delete action is irreversible and removes both the video and JSON assets.
Requests for renders that are still pending, rendering, or failed will be rejected.