Bluesheets fileAI documents API

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

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey18 Endpoints

Install Jentic One Beta

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.

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 fileAI documents 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

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to mark documents as exported, I want to sending files to recognition, Search for construct and return request status, Find all submit change request

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Use Cases

Patterns agents use fileAI documents 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 Jentic?

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

Credential isolation

Your fileAI access token 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 'extract fields from an invoice document' or 'check document processing status', and Jentic returns the matching fileAI 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 fileAI documents 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Bluesheets fileAI documents API

Connect the fileAI documents API to your agent

Capabilities

Start building with fileAI documents API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs