One API for documents, files and audio
File handling often sits between two business systems: an invoice inbox and an ERP, a media upload and an e-shop, or a meeting recording and an internal portal. Skavio provides a common processing API for that step.
One integration pattern
Upload a source file, estimate its credit cost, submit an asynchronous job and retrieve the results. The same pattern covers Flow extraction, supported File Toolbox operations, transcription and Meeting reports.
Your company has one wallet and its own job history. API keys have read or write scopes; secrets are shown once and can be revoked. Result downloads require authentication and company access.
Retries without a second job
Every job submission requires an Idempotency-Key. Repeating the same request with the same key returns the existing job. Changing the request under that key returns a conflict. Use a stable key for one business event and a fresh key when intentionally processing a different event.
Polling or signed callbacks
Check job status from your backend or register a public HTTPS completion webhook. Verify its HMAC signature and timestamp, deduplicate event IDs and acknowledge only after durable receipt. A notification contains result paths; your integration still authenticates to download the files.
Try one bounded workflow
Start with one real file and inspect the returned formats. The developer guide includes curl, Python and JavaScript examples, option details, limits, lifecycle rules and the downloadable OpenAPI contract. Standard processing functions are available through the API; a ready-made connector for every ERP is not implied.