Algodocs API

Name: Algodocs API
Brand: Algodocs API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey10 EndpointsREST

For Agents

Upload PDFs and images to Algodocs, route them to an extractor, and retrieve structured JSON data for invoices, receipts, and other documents.

Install Jentic One Beta

Connect the Algodocs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Algodocs 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Algodocs API.

List the configured extractors in an Algodocs account with /extractors

Upload a document file via multipart with /documents/upload or as base64 with /documents/upload-base64

Inspect documents and their processing status with /documents and /documents/{id}

GET STARTED

Start building with Algodocs API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Algodocs API for, with concrete tasks.

★ Invoice ingestion into accounting

An AP automation flow uploads supplier invoice PDFs to Algodocs by POSTing to /documents/upload with the chosen extractor id, polls /documents/{id} for completion, then pulls the structured JSON via /documents/{id}/extracted-data and writes line items into the accounting system. The integration replaces manual data entry with a controlled, auditable pipeline.

POST /documents/upload with the invoice file and extractor id, poll GET /documents/{id} for status, then GET /documents/{id}/extracted-data and post line items to the accounting system

Receipt capture from a mobile app

A receipt capture mobile app sends base64-encoded images to /documents/upload-base64 alongside the receipt extractor id. Algodocs returns a document id, and the app polls /documents/{id}/extracted-data once processing completes, displaying the parsed merchant, total, and date back to the user.

POST /documents/upload-base64 with the encoded image and extractor id, then GET /documents/{id}/extracted-data once status reports completion

Bulk extracted-data export to a warehouse

A data team exports all extracted data for a given extractor into a warehouse table once a day by calling /extractors/{extractorId}/extracted-data. Because the endpoint already returns structured JSON, the team avoids per-document polling for historical loads.

GET /extractors/{extractorId}/extracted-data with the date range and append the rows to the warehouse table

Agent-driven document parsing through Jentic

A Jentic agent receives an intent like 'extract data from this invoice' along with a file, uploads it to Algodocs, and returns the parsed JSON to the user. The agent never needs to handle the Authorization header - Jentic manages the credential and resolves the right extractor id from the user's account.

Search Jentic for 'extract data from a document', execute POST /documents/upload with the chosen extractor id, then chain GET /documents/{id}/extracted-data to return the structured JSON

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/extractors

List all extractors

POST

/documents/upload

Upload a document for extraction

POST

/documents/upload-base64

Upload a base64-encoded document

GET

/documents/{id}

Retrieve a document and its status

GET

/documents/{id}/extracted-data

Retrieve extracted data for a document

GET

/extractors/{extractorId}/extracted-data

Retrieve all extracted data for an extractor

GET

/extractors

List all extractors

POST

/documents/upload

Upload a document for extraction

POST

/documents/upload-base64

Upload a base64-encoded document

GET

/documents/{id}

Retrieve a document and its status

GET

/documents/{id}/extracted-data

Retrieve extracted data for a document

Why Jentic?

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

Credential isolation

Your Algodocs API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload a document for extraction' or 'retrieve extracted JSON data', and Jentic returns the matching Algodocs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Algodocs API through Jentic.

Why is there no official OpenAPI spec for Algodocs API?

Algodocs does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Algodocs API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Algodocs API use?

Algodocs uses an API key sent in the Authorization request header. Jentic stores the key encrypted in its credential vault and injects the header at execution time so the raw key never enters the agent's prompt or response context.

Can I upload an invoice PDF for extraction with the Algodocs API?

Yes. POST /documents/upload as multipart with the file and the extractor id. Algodocs returns a document id you can poll with GET /documents/{id}; once processing completes, GET /documents/{id}/extracted-data returns the structured JSON.

What are the rate limits for the Algodocs API?

The OpenAPI spec does not declare rate limits. Algodocs enforces plan-based limits server-side, so throttle high-volume document uploads and consider the bulk extracted-data endpoint instead of per-document polling for backfills.

How do I extract data from a document through Jentic?

Search Jentic for 'extract data from a document', load the schema for POST /documents/upload, and execute it with the file and extractor id. Jentic chains the call to GET /documents/{id}/extracted-data once the document completes processing.

Can I send a base64-encoded document instead of a file upload?

Yes. POST /documents/upload-base64 with the encoded payload and the extractor id. This is useful for mobile clients that already hold the file bytes in memory and prefer not to write to disk.

Can I limit what my agent is allowed to do with the Algodocs API?

Yes. Because you run Jentic One yourself, your own rules decide which Algodocs operations and credentials the agent may use. Algodocs puts the extractor and document ids in the URL path, such as GET /extractors/{extractorId}/extracted-data and GET /documents/{id}/extracted-data, so a rule can pin the agent to a single extractor or document. You also choose the operations it may call, so uploading new documents via POST /documents/upload is excluded unless you explicitly allow it.

Algodocs API

Connect the Algodocs API to your agent

Capabilities

Start building with Algodocs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs