Skip to content

Platform overview

The OmniDoc API serves file and content workflows within one account. A caller creates resources with an API key, then uses the stable IDs it gets back to query, combine, process or download them.

ResourcePurpose
Document / FileSource files and file library entries owned by the account
Job / OperationAsynchronous translation, document processing or audio and video jobs
ArtifactResults a job delivers for preview or download
Credit operationThe record of what one billable action charged and refunded

Every resource is checked against the owning account. Clients only need to keep public IDs, and should not infer implementation details from IDs, file names or download addresses.

  1. Create or choose an input resource.
  2. Make sure the account has credits: the balance is checked against a threshold before the job starts, and actual usage is charged when it finishes.
  3. Create the job with an Idempotency-Key.
  4. Check the job status; file translation jobs can also use SSE or webhooks.
  5. Read the results and the credit record for this job.

External integrations always use API keys, with the same permissions as the account that created the key. See authentication.