Ruwana Developer Documentation
Build with the live Ruwana Video API.
One authenticated endpoint exposes two production modes: image-to-video and text-to-video. Platform keeps their input rules, resolution truth, audio semantics and durable lifecycle explicit.
| Mode | Input contract | Delivery | Audio |
|---|---|---|---|
| I2V | Start Frame required; End optional; Bind and Multi-Shot supported | 1080p $0.22/s · 4K $0.30/s | Optional +$0.08/s |
| T2V | No Start/End; aspect 16:9, 9:16 or 1:1 | 1080p $0.28/s · 4K $0.34/s | Capability included |
Shared request lifecycle
POST /v1/video/generate
Authorization: Bearer $RUWANA_API_KEY
Idempotency-Key: your-stable-request-key
GET /v1/requests/{requestId}
Duration: 3–15 seconds
Multi-Shot: 2–6 ordered shots, total 3–15 seconds
Platform delivery: 1080p or 4K
Media retention: 7 daysStart & End
I2V preserves explicit opening and optional closing visual targets. End Frame is never valid without Start Frame.
Bind
I2V can bind entitled Ruwana model identities and bounded custom visual elements, with a maximum of three total bound elements in Video API v1.
Multi-Shot
Ordered shot direction can vary by segment while bound elements remain continuous across the production.
Need the production overview?
The Video API page covers the creative/production contract and pricing; these docs focus on implementation.