@clipwright/sdk
TypeScript client for the Clipwright UGC video API.
import { ClipwrightClient } from "@clipwright/sdk";
const client = new ClipwrightClient({ apiKey: process.env.CLIPWRIGHT_API_KEY! });
const quote = await client.quoteUgc({ script: "Hello from Clipwright." });
const run = await client.makeUgc({ script: "Hello from Clipwright." });
makeUgc renders a clip and costs money; quoteUgc does not. Every call
carries an idempotency key derived from the input and from this installation's
id, so a retried request returns the original run instead of paying twice. Pass
idempotencyKey explicitly when you deliberately want a fresh run.
Requires CLIPWRIGHT_CLIENT_ID, or a writable ~/.clipwright/ for the SDK to
create one on first use. It fails loudly rather than generating a throwaway id,
because a per-process id would disable duplicate protection without saying so.
Deadlines cancel the request (behaviour change)
fetch has no default timeout in Node, so until this release a connection that
was accepted and then went silent — a proxy dying between you and the API — hung
forever. maxWaitMs did not save you: it was checked between status polls, so
control never came back to it.
Two deadlines now abort the request itself, not just the wait:
maxWaitMs (per makeUgc call, default 10 min) bounds the whole call,
including the request in flight when it expires.
requestTimeoutMs (per client, default 30 s) bounds every single request.
const client = new ClipwrightClient({
apiKey: process.env.CLIPWRIGHT_API_KEY!,
requestTimeoutMs: 60_000,
});
What changes for you: a call that used to hang now rejects. A makeUgc
whose polling is cut short still throws the same timeout error, naming the run
so you can pick it up later with getRun. A start request aborted mid-flight
throws ClipwrightResponseError with mayHaveTakenEffect: true and
deliveryConfirmed: false — the run may exist and may be charged, so check your
recent runs instead of retrying with a fresh idempotency key. Requests on the
free paths (quoteUgc, listVoices, getRun) reject with a TimeoutError
DOMException; retrying them is safe.
Raise requestTimeoutMs if you sit behind a slow proxy; it must stay positive,
and a non-positive or non-finite value is rejected loudly rather than replaced
with the default.
Changelog
What changed in each release, and what was removed, is in CHANGELOG.md inside
this package. Read its Breaking: entries before upgrading.