Migrate from API v1 to v2

Move from the synchronous conversion endpoint to managed documents, immutable revisions, jobs, and private artifacts.

Lifecycle difference

The v1 endpoint returns a PDF in one request. API v2 separates durable source, rendering work, and artifact delivery so retries, deletion, provenance, and automation are explicit.

Migration sequence

Create the document once, create a new revision for each source update, and publish the intended revision with a stable idempotency key.

Controlled cutover

Keep v1 and v2 integrations side by side during validation. Compare the source, selected template, page count, and artifact digest before moving production traffic.

APIアクセスを確認中

有効化状態を読み込んでいます。