IETF RFC 9110: HTTP Semantics, §9.2.2

Know the processing cost before submitting the job. Skavio Processing API supports fixed company-credit quotes, atomic credit reservations, idempotent job submissions and authenticated result downloads. This guide outlines a Flow invoice-extraction workflow—from preparing company access to reviewing the exported data—without assuming unverified request syntax.

1. Prepare company access—not a personal subscription

Skavio Processing API is a server-side HTTPS API with scoped keys and company-isolated jobs. Begin with company access and a key scoped to the operations your integration needs. Company credits are separate from existing personal web plans; do not assume a personal subscription funds company API jobs. Keep credentials in server-side configuration, not browser code or request URLs. OWASP recommends HTTPS for REST endpoints and warns that API keys in URLs can enter server logs. This is general security guidance, not a claim of Skavio certification. This walkthrough describes the integration sequence, not verified request syntax. Before implementation, confirm authentication, operations and required fields in the documentation at https://www.skavio.eu/api/docs/ and the OpenAPI contract at https://www.skavio.eu/api/openapi.json.

2. Upload a synthetic invoice first

Start with a synthetic invoice containing representative dates, totals and line items. This lets you test the workflow without putting customer data into development examples. Use the documented upload operation, then prepare a Flow extraction request with the fields your application needs. Flow outputs include XLSX document and line-item worksheets, CSV, JSON, source evidence and review warnings. Choose outputs for your next step: a spreadsheet for review, structured JSON for application logic, or CSV for an agreed import process. Check the upload and storage limits before attempting a larger batch. An upload allowance is not a promise that every file will process concurrently.

Upload limits: up to 100 files and 500 MB total.
PDF limit: 100 pages; company source-storage limit: 2 GB.
Keep credentials, personal data and private paths out of test logs and screenshots.

3. Request the server quote before submitting work

Obtain the server quote for the intended processing request before submitting the job. Local arithmetic is useful for planning, but the server quote should determine the actual submission cost. Flow extraction costs 100 company credits per page, with a minimum of 200 credits per document, including OCR and export. A one-page invoice therefore illustrates the minimum—not a 100-credit job. For multiple documents, account for the minimum on each document. Flow offers 1,000 trial credits per company, with no card required. Paid credits never expire, while monthly company credit plans remain capped. These are credit allowances, not unlimited processing.

Illustrative one-page invoice: 200 credits.
Illustrative three-page invoice: 300 credits.
Confirm quote validity and how the quote is used when submitting a job in the API documentation.

4. Submit idempotently, then track completion

Follow the documentation to submit the quoted processing job using the API's idempotency mechanism. Skavio reserves the fixed quote atomically, consumes the reserved credits on success and releases the reservation once on failure. Idempotency matters when a connection fails after submission: a timeout alone does not establish whether the server accepted the work. Confirm Skavio's replay behavior before implementing retries. RFC 9110 cautions against automatically retrying non-idempotent requests unless their semantics are known to be idempotent or the original request was never applied. Track the job through the documented completion mechanism. The API supports signed completion webhooks; verify the signature procedure before relying on webhook notifications. Plan around the operating limits rather than assuming parallel execution.

Request limit: 120 per minute.
Company queue: up to 100 jobs, with one active company job.
Verify the idempotency field, replay rules and completion states before implementing retries.

5. Download with authentication—and review before import

Once processing completes, retrieve the results through the documented authenticated download operation. Do not assume results are available through a public URL. Keep download credentials server-side and store the outputs your application needs in your own controlled system. The verified snapshot lists a seven-day retention period. Retrieve results promptly and confirm the exact expiry behavior in the documentation; the supplied facts do not establish when that period begins. For invoice extraction, a successful job is not the same as approved accounting data. Review dates, totals and line items, using source evidence and review warnings to investigate discrepancies. Only then pass the approved output into your downstream workflow. The Processing API provides processing capabilities; it does not imply a built-in ERP connector or automatic posting.

Use local arithmetic to plan; use the server quote to commit the job.

Sources

Skavio Processing API — supplied product snapshot — The supplied 1 October 2026 snapshot establishes server-side HTTPS access, scoped keys, company-isolated jobs, fixed quotes, atomic credit reservations, idempotent submissions, signed completion webhooks, authenticated downloads and operating limits. These facts were not independently retrieved from the linked page.
Skavio Processing API documentation and OpenAPI contract — Official documentation address supplied by Skavio. The supplied OpenAPI address is https://www.skavio.eu/api/openapi.json. Exact request fields, authentication syntax, quote validity, replay behavior and completion states remain unverified.
Skavio Flow — supplied product snapshot — The supplied snapshot specifies Flow outputs, source evidence and review warnings, 1,000 trial credits per company with no card required, and extraction pricing of 100 credits per page with a 200-credit minimum per document including OCR and export. The supplied 2 October 2026 credit policy confirms the extraction rate.
OWASP REST Security Cheat Sheet — The research brief cites this guidance for HTTPS REST endpoints and keeping API keys out of request URLs because URLs can enter server logs.
IETF RFC 9110: HTTP Semantics, §9.2.2 — The research brief cites this standard for idempotency and its caution against automatically retrying non-idempotent requests unless their semantics are known to be idempotent or the original request was never applied.

Open the Processing API documentation and test a Flow extraction