fileAI documents API

Name: fileAI documents API API
Brand: fileAI documents API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey18 EndpointsREST

For Agents

Programmatically mark documents as exported, sending files to recognition. Covers 18 operations with apiKey authentication.

Connect the fileAI documents API to your agent

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

Mark documents as exported

sending files to recognition

construct and return request status

submit change request

GET STARTED

Start building with fileAI documents API API

Explore with Jentic

View OpenAPI Document

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

This is an API that is aimed to simplify managing documents. If you have any questions about the API that are not covered in the following documentation, please click "Contact the developer" link underneath. > Please, be aware that you need API key for accessing the API. You can get API keys through fileAI web-interface in the 'API Keys' section. As soon as you obtain your API key, you should incl. The API exposes 18 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use fileAI documents API API for, with concrete tasks.

★ CRM Operations

Use the fileAI documents API to perform crm operations programmatically. The API provides 18 endpoints covering core functionality including mark documents as exported, sending files to recognition, construct and return request status.

Call POST /documents/markDocumentsExported to mark documents as exported

Automated Document Endpoints Management

Automate document endpoints operations by combining multiple fileAI documents API endpoints. Agents can sending files to recognition and then construct and return request status in a single workflow.

Call POST /documents/extract to sending files to recognition, then verify the result

AI Agent Integration via Jentic

AI agents discover and call fileAI documents API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'mark documents as exported', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

18 endpoints — this is an api that is aimed to simplify managing documents.

METHOD

PATH

DESCRIPTION

POST

/documents/markDocumentsExported

Mark documents as exported

POST

/documents/extract

sending files to recognition

POST

/documents/status

construct and return request status

POST

/documents/changeRequest

submit change request

POST

/documents/importJsonData

import json data to fileAI system

POST

/v2/userDocumentTypes

create create tags into organization

POST

/v2/documents/changeRequest

submit change request

POST

/v2/documents/extract

sending files to recognition

POST

/documents/markDocumentsExported

Mark documents as exported

POST

/documents/extract

sending files to recognition

POST

/documents/status

construct and return request status

POST

/documents/changeRequest

submit change request

POST

/documents/importJsonData

import json data to fileAI system

Why though Jentic?

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

Credential isolation

fileAI documents API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'mark documents as exported') and Jentic returns the matching fileAI documents API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct fileAI documents API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Hubspot

Alternative crm API

Choose Hubspot when you need a different approach to crm operations

Alternative

Salesforce

Alternative crm API

Choose Salesforce when you need a different approach to crm operations

Complementary

Pipedrive

Complementary crm API

Choose Pipedrive when you need a complementary approach to crm operations

Complementary

Zoho

Complementary crm API

Choose Zoho when you need a complementary approach to crm operations

FAQs

Specific to using fileAI documents API API through Jentic.

What authentication does the fileAI documents API use?

The fileAI documents API uses an API key passed in the `access_token` query. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I mark documents as exported with the fileAI documents API?

Yes. Use the POST /documents/markDocumentsExported endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the fileAI documents API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I mark documents as exported through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'mark documents as exported'. Jentic returns the matching fileAI documents API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the fileAI documents API have?

The fileAI documents API exposes 18 endpoints covering document endpoints operations.