Renduo
Api referenceAssets

Delete an asset from the registry

Does not affect any already-baked version: the asset was inlined as a data URI inside its shell (ADR-016 §2.4). It only prevents declaring it in future versions.

DELETE
/v1/assets/{name}

Authorization

apiKey
AuthorizationBearer <token>

Renduo API key sent as Authorization: Bearer rnd_live_XXXXXXXXXXXX (or rnd_test_... in test mode). See GET /v1/auth/me.

In: header

Path Parameters

name*string

Response Body

application/json

application/json

curl -X DELETE "https://example.com/v1/assets/string"
{}
{  "error": "string",  "message": "string",  "details": {},  "requestId": "string"}

Upload a custom asset (font or image) POST

multipart/form-data with the file in the "file" field and the asset name in "name". Uploading with an existing name replaces the asset (already-baked shells do not change — ADR-016 §2.4).

Generate a PDF POST

Generates a PDF. Two body variants: `{templateId, payload, version?, mode}` against a registered component-first template (sync mode waits and returns the PDF as base64, timeout 10000ms, ephemeral; async mode enqueues and notifies through the webhooks registered in Settings, ADR-015), or `{bundle, payload}` — ephemeral inline mode (ADR-010, in-app editor): a bundle IIFE already compiled in the browser, without registering any template. Always sync, never persists anything (neither the bundle, nor the payload, nor the PDF, nor a Generation row) — the 200 response of this mode does not include `generationId`. Required scope: generate.