Vantage processing REST API

Name: Vantage processing REST API API
Brand: Vantage processing REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLVisionoauth231 EndpointsREST

For Agents

Submit documents to ABBYY Vantage skills and retrieve structured field extractions via OAuth 2.0. Use it to automate invoice, receipt, and form processing.

Quickstart

Get started with Vantage processing REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"extract structured data from an invoice"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Vantage processing REST API API.

Start a processing transaction and attach source files for a chosen skill

Trigger skill execution and poll until extraction completes

Retrieve extracted fields, confidence scores, and the source page mapping

Manage catalogs of reference records used during extraction (e.g., vendor lists)

GET STARTED

Start building with Vantage processing REST API API

Explore with Jentic

View OpenAPI Document

Use for: I need to extract line items from a PDF invoice, Submit a batch of receipts to ABBYY Vantage and get the extracted totals, List all skills available in my Vantage tenant, Add 500 vendor records to a catalog used by an invoice skill

Not supported: Does not handle e-signing, document storage as a primary system of record, or generative AI text generation — use for OCR-driven document processing and field extraction only.

Jentic publishes the only available OpenAPI document for Vantage processing REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Vantage processing REST API, keeping it validated and agent-ready. ABBYY Vantage is an intelligent document processing platform that turns unstructured documents into structured data using configurable skills (invoices, receipts, IDs, custom forms). The Vantage processing REST API exposes 31 endpoints to start transactions, upload source files, attach catalogs, run skills, and retrieve extracted document fields. It supports the US, EU, and Australia hosting regions and is gated by OAuth 2.0.

Use Cases

Patterns agents use Vantage processing REST API API for, with concrete tasks.

★ Invoice Data Extraction

Finance teams want to convert inbound invoice PDFs into structured records ready for AP automation. The Vantage processing REST API supports the full flow: POST /transactions creates the transaction, the documents and sourceFiles endpoints attach the PDF, and the result endpoints return supplier, totals, and line items as JSON. Confidence scores let downstream systems route low-confidence rows to human review.

Create a Vantage transaction for the invoice skill, attach invoice.pdf, run the skill, and return the extracted vendor name and total amount

ID and KYC Document Processing

Compliance workflows process passports, driving licences, and national IDs to populate KYC records. ABBYY Vantage provides skills tuned to ID layouts in many countries; the REST API drives them with the same transaction-and-document pattern. Catalog endpoints can validate extracted fields against an internal allow list before the record is persisted.

Run the ID skill on a passport scan, extract the document number and expiry, and validate them against an internal catalog

Catalog-Backed Validation

Many extraction projects need to match free-text fields (vendor name, GL code, country) against a controlled list. The catalog endpoints under /catalogs/{catalogId}/records support adding, deleting, and prefix-searching records, and the reindex endpoint refreshes the search index after bulk changes. This keeps extraction outputs aligned with the customer's master data.

Add 500 supplier records to catalog ID 'suppliers', call the reindex endpoint, and verify with a prefix search for 'Acm'

Agent-Driven Document Processing via Jentic

AI agents pick up document jobs from a queue and want a single tool call to extract structured data. Through Jentic, an agent searches for an extraction intent, loads the Vantage operation, and executes the transaction lifecycle without managing OAuth refresh logic. This collapses a multi-step direct integration into a few agent calls.

Search Jentic for 'extract data from an invoice', load the Vantage skill operation, attach the file, and return structured fields

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for vantage processing rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/publicapi/v1/transactions

Create a processing transaction

POST

/api/publicapi/v1/transactions/{transactionId}/documents

Create a document inside a transaction

POST

/api/publicapi/v1/transactions/{transactionId}/documents/{documentId}/sourceFiles

Attach a source file to a document

GET

/api/publicapi/v1/skills

List available skills

GET

/api/publicapi/v1/catalogs/{catalogId}/search

Prefix-search records in a catalog

POST

/api/publicapi/v1/catalogs/{catalogId}/reindex

Reindex a catalog after bulk changes

POST

/api/publicapi/v1/transactions

Create a processing transaction

POST

/api/publicapi/v1/transactions/{transactionId}/documents

Create a document inside a transaction

POST

/api/publicapi/v1/transactions/{transactionId}/documents/{documentId}/sourceFiles

Attach a source file to a document

GET

/api/publicapi/v1/skills

List available skills

GET

/api/publicapi/v1/catalogs/{catalogId}/search

Prefix-search records in a catalog

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ABBYY Vantage OAuth client secrets are stored encrypted in the Jentic vault. Agents call operations by ID and Jentic mints and refreshes access tokens at execution time, so secrets never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'extract data from an invoice') and Jentic returns the matching Vantage transaction operation along with its input schema, including the skill ID parameter.

Time to first call

Direct integration: 3-5 days to handle OAuth, transaction lifecycle, and polling across the 31 endpoints. Through Jentic: under 2 hours — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AWS Textract

AWS's OCR and document analysis service for forms, tables, and queries.

Choose Textract when the workload is on AWS and basic forms/tables extraction is enough; use Vantage when skills, catalogs, and human-in-the-loop tooling matter.

Alternative

Google Cloud Vision

Google's vision API for OCR, document text detection, and image labelling.

Pick Vision for general OCR and image understanding; pick Vantage when domain-specific skills (invoices, IDs) and catalog validation are required.

Alternative

Mindee

Mindee's parsing APIs for invoices, receipts, IDs, and custom documents.

Use Mindee for fast document-type APIs without configuring skills; Vantage when catalogs and tenant skills are core.

Alternative

Rossum

Rossum's transactional document automation API focused on invoices.

Pick Rossum for invoice-heavy AP automation; pick Vantage for broader document types and on-prem/region deployment.

FAQs

Specific to using Vantage processing REST API API through Jentic.

Why is there no official OpenAPI spec for Vantage processing REST API?

ABBYY publishes Vantage reference docs but not a discoverable OpenAPI specification at the catalog level. Jentic generates and maintains this spec so that AI agents and developers can call Vantage processing REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Vantage processing REST API use?

The API uses OAuth 2.0 via the OAuth2Security scheme. Clients exchange tenant credentials for an access token and pass it as a bearer token. Through Jentic, the OAuth secret stays in the Jentic vault and tokens are minted at execution time, so the agent never holds the raw secret.

Can I extract data from invoices with the Vantage processing REST API?

Yes. Create a transaction with POST /api/publicapi/v1/transactions for the invoice skill, attach the file via the documents and sourceFiles endpoints, then poll the transaction until the extracted document is available with structured supplier, totals, and line-item fields.

How do I list the skills available in my Vantage tenant?

Call GET /api/publicapi/v1/skills for a list, or GET /api/publicapi/v1/skills/{skillId} for the schema of a single skill. The schema describes the input options and output fields the extraction will return.

How do I run a Vantage extraction through Jentic?

Search Jentic for 'extract data from a document', load the Vantage transaction operation, and execute it with the skill ID and file. Jentic handles OAuth refresh and returns the structured extraction once processing completes.

What hosting regions does the Vantage processing REST API support?

The spec lists three base URLs: https://vantage-us.abbyy.com, https://vantage-eu.abbyy.com, and https://vantage-au.abbyy.com. Choose the region that matches your tenant; the endpoint paths are identical across regions.