Convoflo API

Name: Convoflo API API
Brand: Convoflo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDocument Managementbearer109 EndpointsREST

For Agents

Create file requests, manage secure document folders, track file versions, and approve client document submissions on Convoflo. Agents authenticate with a bearer token.

Quickstart

Get started with Convoflo 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:
"create a convoflo file request from a client"

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

Capabilities

What an agent can do with Convoflo API API.

Create and manage file requests with POST /api/1/folders/{userFolder}/file-requests and the /api/1/file-requests endpoints

Approve or reject individual request items via /file-requests/{fileRequestId}/items/{fileRequestItem}/approve or /reject

Maintain reusable file request templates under /api/1/file-request-templates

Manage documents — favourite, follow, update metadata, list versions, and delete — via /api/1/documents/{userFile}

GET STARTED

Start building with Convoflo API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Convoflo API, keeping it validated and agent-ready. Convoflo is a client messaging and secure file-sharing platform built around an email-like interface, primarily used by professional services firms exchanging documents with clients. The 109 endpoints cover file requests, secure space folders, document and version management, file request templates, account profile, and organisation-level operations. Authentication is HTTP bearer.

Use Cases

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

★ Client Document Request Workflow

Send templated requests for documents (KYC packs, tax returns, signed agreements) and track submissions through to approval. Create a request via POST /api/1/folders/{userFolder}/file-requests, attach items, and use the approve and reject endpoints as the client uploads files. Suited to legal, accounting, and financial services firms onboarding clients with predictable document checklists.

Create a file request in folder 42 with three required items (ID, proof of address, signed engagement) and email the client the link

Document Lifecycle and Audit Trail

Track every interaction with a sensitive document — opens, downloads, version uploads, favourites — using /api/1/documents/{userFile}/timeline plus the version listing endpoint. The audit trail is essential for regulated industries that must prove who accessed which document and when. Useful for compliance and ops teams reviewing access logs as part of audits.

Pull the timeline for the document attached to engagement 9876 and produce a CSV of all access events in the last 30 days

Reusable File Request Templates

Codify recurring document checklists (annual review, new hire onboarding, loan application) as Convoflo file request templates so reps can launch a new client request in seconds. Templates are managed under /api/1/file-request-templates and instantiated against any secure space folder. Reduces handover errors and keeps document collection consistent across the firm.

Create a file request template named 'Annual Tax Pack' with required items for prior year return, W-2s, and 1099s

Agent-Driven Client Document Collection via Jentic

An AI agent runs the full client document loop through Jentic — instantiate a template, send the request, monitor submissions, and approve or reject items. Through Jentic the bearer token sits in the vault so the agent can run document collection automations at scale without holding the secret. The agent searches for the file-request intent, loads the schema, and chains the calls.

Search Jentic for 'create a Convoflo file request', load the schema, instantiate the 'Annual Tax Pack' template for client folder 42, and notify Slack when all items are approved

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/1/folders/{userFolder}/file-requests

Create a file request in a secure space

GET

/api/1/file-requests

List the user's file requests

POST

/api/1/file-requests/{fileRequestId}/items/{fileRequestItem}/approve

Approve a submitted file request item

POST

/api/1/file-requests/{fileRequestId}/items/{fileRequestItem}/reject

Reject a submitted file request item

GET

/api/1/documents/{userFile}/timeline

List activity events for a document

POST

/api/1/file-request-templates

Create a reusable file request template

POST

/api/1/folders/{userFolder}/file-requests

Create a file request in a secure space

GET

/api/1/file-requests

List the user's file requests

POST

/api/1/file-requests/{fileRequestId}/items/{fileRequestItem}/approve

Approve a submitted file request item

POST

/api/1/file-requests/{fileRequestId}/items/{fileRequestItem}/reject

Reject a submitted file request item

GET

/api/1/documents/{userFile}/timeline

List activity events for a document

Why though Jentic?

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

Credential isolation

Convoflo bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access at execution time and the token is injected into the Authorization header — raw tokens never enter the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a Convoflo file request') and Jentic returns the matching POST /api/1/folders/{userFolder}/file-requests or related operation with its input schema.

Time to first call

Direct Convoflo integration: 2-3 days across 109 endpoints, file request lifecycle, and webhook setup. Through Jentic: under 1 hour — search, load, execute the chained flow.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Box API

Enterprise content management with file collaboration, broader scope than Convoflo's client-portal model.

Choose Box for general enterprise file collaboration; pick Convoflo for client-facing structured document requests with templates.

Alternative

Dropbox API

Cloud file storage and sharing with team folders, similar storage scope but no client-portal abstraction.

Choose Dropbox for general file storage and sync; pick Convoflo when client document collection workflows and approvals are core.

Complementary

Dropbox Sign API

E-signature platform that pairs with Convoflo when collected documents need countersignatures.

Pair with Convoflo when a collected document (engagement letter, contract) must be signed before final approval.

FAQs

Specific to using Convoflo API API through Jentic.

Why is there no official OpenAPI spec for Convoflo API?

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

The API uses HTTP bearer authentication. Send the token in the Authorization: Bearer header on every call to /api/1/* endpoints. Through Jentic the token is stored encrypted in the vault and injected at execution time so it never appears in the agent's prompt context.

How do I create a file request from a client with the Convoflo API?

POST /api/1/folders/{userFolder}/file-requests creates the request inside a secure space, then POST /api/1/file-requests/{fileRequestId}/items attaches the items the client must supply. POST /api/1/file-requests/{fileRequestId} finalises the request once all items are configured.

Can I approve or reject specific items on a file request?

Yes. POST /api/1/file-requests/{fileRequestId}/items/{fileRequestItem}/approve marks an individual item as accepted, while .../reject marks it rejected and prompts the client to resubmit. Use this to enforce per-item gating during document review.

How do I see who has accessed a Convoflo document?

GET /api/1/documents/{userFile}/timeline returns the activity timeline including views, downloads, comments, and version updates for a specific document. Pair with the file versions endpoint for a complete audit trail.

What are the rate limits for the Convoflo API?

Rate limits are not declared in the OpenAPI spec. Treat the file request and document endpoints as soft-limited per bearer token and back off on HTTP 429 responses. Contact Convoflo support for documented limits applicable to your plan.

How do I create a Convoflo file request through Jentic?

Run jentic search for 'create a Convoflo file request', load the POST /api/1/folders/{userFolder}/file-requests operation, and execute it with the secure space folder ID and the items to collect. Jentic injects the bearer token from the vault and returns the new request ID as a structured response.