renza

API reference / Imports

Import a deck

POST/v1/imports

Parses the slide contract, stores the HTML, and creates a deck + artifact (+ slides). With `external_id`, re-importing adds a new artifact version to the same deck.

Requires an API key (bearer), scoped to the active org. Supports idempotency keys.

Body parameters

  • sourcestringrequired

    Possible values: upload, paste

  • htmlstringoptional

    Single-file: the raw deck HTML. Provide this OR `files`.

  • filesarray of objectoptional

    Multi-file bundle (entry HTML + its assets); the entry is auto-detected. Provide this OR `html`. ~3 MB total cap — larger bundles use the web uploader.

  • titlestringoptionalmax 300 chars
  • external_idstringoptionalmax 200 chars

    Reuse + version the deck with this id (update-in-place). Omitted → the server derives a FRESH id from the title (never touching an existing deck) and returns it as `external_id`; republish with it to version the same deck at the same link.

Returns

  • 201The completed import (deck + artifact created).

Failures use the standard error envelope with a closed set of codes.