Koncile API

Name: Koncile API API
Brand: Koncile API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLMl Inferencebearer25 EndpointsREST

For Agents

Upload business documents to Koncile, run template-based extraction, and pull structured field data through async tasks.

Connect the Koncile API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Koncile API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Koncile API API.

Upload an invoice or receipt file to a Koncile folder for extraction

Poll for the result of an async extraction task

Create or update an extraction template with custom fields

Add fields and field instructions to refine extraction accuracy

GET STARTED

Start building with Koncile API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Koncile API, keeping it validated and agent-ready. Koncile is a document data extraction service that converts invoices, receipts, and other business documents into structured fields using AI templates. The API exposes file upload, async task results, folders that group documents, templates and their fields and instructions, plus document and field-data retrieval. It suits finance, AP, and operations teams who want to script invoice ingestion or build a custom UI on top of Koncile's extraction engine.

Use Cases

Patterns agents use Koncile API API for, with concrete tasks.

★ Automated Invoice Ingestion for AP Teams

Replace manual invoice keying with a Koncile pipeline that uploads PDFs, runs template extraction, and writes fields into the accounts-payable system. POST /v1/upload_file/ accepts the document, /v1/fetch_tasks_results/ polls for completion, and /v1/fetch_document_data/ returns the structured fields. This is a common workflow for finance teams that receive hundreds of supplier invoices per month.

Upload supplier-invoice.pdf via POST /v1/upload_file/, poll /v1/fetch_tasks_results/ until status is complete, then return total_amount and supplier_name from /v1/fetch_document_data/.

Custom Template Creation for New Document Types

Stand up extraction for a new document type — purchase orders, contracts, expense receipts — by scripting template creation. POST /v1/create_template/ defines the template, /v1/create_field/ adds fields, and /v1/create_instruction/ refines extraction logic. Useful when an operations team needs to onboard a new vendor's document format without going through the Koncile UI.

Create a template named 'shipping-bill', add fields 'tracking_number' and 'shipping_cost', then add an instruction telling Koncile that 'shipping_cost' appears under the 'Total Charges' label.

Folder-Based Batch Processing

Group related documents into a folder so an automation can process them as a batch. /v1/create_folder/ creates the folder, uploads target it, and /v1/fetch_documents/ enumerates the contents for downstream steps. Suited for monthly closing cycles where a team drops dozens of receipts into one bucket and needs everything extracted before reconciliation.

Create a folder named 'may-receipts-2026' and list all documents in it via /v1/fetch_documents/.

Field-Level Quality Loop

Improve extraction quality by inspecting and adjusting fields and instructions over time. /v1/fetch_field/ and /v1/fetch_instruction/ surface the current configuration, which an agent can review against actual extraction errors. This makes Koncile usable as a self-improving pipeline rather than a black box.

Fetch the instructions for template 'supplier-invoices' via /v1/fetch_instruction/ and report any fields that have no instruction defined.

Agent-Driven Document Pipeline via Jentic

Have an AI agent run the full Koncile pipeline — upload, poll, fetch — when a finance teammate forwards an invoice email. The agent searches Jentic for the matching Koncile operation, loads the schema, and executes with the bearer token kept in the Jentic vault. Removes glue code that would otherwise stitch together upload, polling, and field retrieval.

Through Jentic, search for 'extract data from a Koncile invoice', load /v1/upload_file/, upload invoice.pdf, poll for the result, and return the parsed fields.

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for koncile api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/upload_file/

Upload a document for extraction

POST

/v1/fetch_tasks_results/

Fetch the result of an async task

POST

/v1/fetch_document_data/

Retrieve extracted field data for a document

POST

/v1/create_template/

Create an extraction template

POST

/v1/create_field/

Add a field to a template

POST

/v1/create_folder/

Create a folder for grouping documents

POST

/v1/fetch_documents/

List documents inside a folder

POST

/v1/check_api_key/

Validate an API key

POST

/v1/upload_file/

Upload a document for extraction

POST

/v1/fetch_tasks_results/

Fetch the result of an async task

POST

/v1/fetch_document_data/

Retrieve extracted field data for a document

POST

/v1/create_template/

Create an extraction template

POST

/v1/create_field/

Add a field to a template

Why though Jentic?

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

Credential isolation

Koncile bearer tokens are stored encrypted in the Jentic vault. Agents call /v1/upload_file/, /v1/fetch_tasks_results/, and /v1/fetch_document_data/ through scoped Jentic tools without holding the raw token.

Intent-based discovery

Agents search by intent (e.g., 'extract invoice data', 'create a Koncile template') and Jentic returns the matching operation from the 25-endpoint surface so the agent calls the right one without reading the docs.

Time to first call

Direct Koncile integration: 2-3 days to wire upload, async polling, and template management. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mindee API

Document AI platform with prebuilt invoice and receipt parsers

Choose Mindee when prebuilt parsers cover the document types in scope; choose Koncile when custom templates and instructions matter.

Alternative

Rossum API

Cognitive document processing platform aimed at high-volume AP

Use Rossum for enterprise AP at very high volumes; use Koncile for lighter-weight integrations and per-template tuning.

Complementary

Airtable API

Common destination for the structured fields Koncile extracts

Use Airtable as the analyst-facing store of extracted fields after Koncile parses the underlying invoices.

FAQs

Specific to using Koncile API API through Jentic.

Why is there no official OpenAPI spec for Koncile API?

Koncile does not publish a complete OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Koncile 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 Koncile API use?

The Koncile API uses HTTP Bearer authentication. The bearer token is sent in the Authorization header on every request. Through Jentic, the token is held in the Jentic vault and injected at execution time so the agent never sees the raw value. /v1/check_api_key/ can confirm a token is active.

How does Koncile's async extraction work?

POST /v1/upload_file/ submits a document and returns a task id. The actual extraction runs asynchronously. Poll /v1/fetch_tasks_results/ with the task id until the status is complete, then call /v1/fetch_document_data/ to retrieve the structured fields.

What are the rate limits for the Koncile API?

Koncile does not publish a public rate limit and the spec does not declare one. Treat upload and poll endpoints as moderately throttled; back off when /v1/fetch_tasks_results/ indicates a queued task instead of polling tightly.

How do I extract fields from an invoice through Jentic?

Search Jentic for 'extract data from a Koncile invoice', load /v1/upload_file/, and execute with the file. Jentic chains the upload, /v1/fetch_tasks_results/ polling, and /v1/fetch_document_data/ retrieval so the agent receives the parsed fields in one tool call.

Can I add custom fields to a Koncile template via the API?

Yes. POST /v1/create_field/ adds a field to an existing template, and /v1/create_instruction/ adds an instruction that tells Koncile how to recognise that field on real documents. Use this to onboard new document types without the dashboard.