Skip to main content
POST
Queue a file conversion
See conversion formats and limits for integration guidance. This call returns an admission receipt. Poll the get endpoint until work stops, then inspect the result and download its artifacts. See job lifecycle.

TypeScript

Authorizations

Authorization
string
header
required

Revise API key from https://revise.io/console/api-keys. Send Authorization: Bearer .

Headers

Idempotency-Key
string
required
Required string length: 1 - 200

Body

application/json
input
object
required
output
object
required
limits
object

Optional execution and spending thresholds. Spending limits are opt-in: omitted cost limits are unlimited. The time limit defaults to 900 seconds. Prompt platform cost is base fee plus tool CPU; conversion platform cost is its flat/page fee. Prompt cost limits may each be at most $500,000; conversion cost limits may each be at most $1,000,000. These thresholds do not reserve account credit.

Example:
inference
object
metadata
object

Up to 16 string values for application attribution. Keys are 1–64 UTF-8 bytes; values at most 512 UTF-8 bytes. Metadata is deleted with request content; persist your own job mapping for long-term attribution.

Example:
output_encryption
object

Encrypt exported artifact bytes using compact JWE, RSA-OAEP-256 and A256GCM. Only encrypted files are downloadable. Disables prompt continuation and artifact reuse; cannot be combined with previous_prompt_id or artifact_id input. Prompts require editing or export_document=true.

retention
object

Response

Queued conversion

id
string
required
object
any
required
status
enum<string>
required
Available options:
queued,
running,
succeeded,
failed,
cancelled
mode
enum<string>
required

Empty after request content has been deleted.

Available options:
deterministic,
vision,
input
object
required
output
object
required
output_encrypted
boolean
required
metadata
object
required

Up to 16 string values for application attribution. Keys are 1–64 UTF-8 bytes; values at most 512 UTF-8 bytes. Metadata is deleted with request content; persist your own job mapping for long-term attribution.

Example:
usage
object | null
required

Customer-facing settled charges and usage. Supplier costs, margins and internal reconciliation diagnostics are not exposed. Historical charges are never recalculated using current prices.

Example:
created_at
string<date-time>
required
completed_at
string<date-time> | null
required
content_expires_at
string<date-time> | null
required
content_deleted_at
string<date-time> | null
required
error
object | null
required
retention
object