How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Flowise

Flowise document-store API

The document-store API from Flowise — 9 operation(s) for document-store.

Documentation Provider Profile APIs.io OpenAPI GitHub

Flowise document-store API is one of 13 APIs that Flowise publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Document Store. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 13 operations across 9 paths, and defines 9 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: http://localhost:3000/api/v1, https://{instance}.flowiseai.com/api/v1.

13 operations 9 paths 9 schemas 4 DELETE3 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
http://localhost:3000/api/v1
Authentication
HTTP Bearer
Contact
FlowiseAI
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

Flowise document-store API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 13

Across 9 paths, the API surfaces 13 operations — 4 DELETE, 3 GET, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

document-store 13
POST
/document-store/store
Create a new document store
createDocumentStore body → 200400500
GET
/document-store/store
List all document stores
getAllDocumentStores → 200500
GET
/document-store/store/{id}
Get a specific document store
getDocumentStoreById 1 param → 200404500
PUT
/document-store/store/{id}
Update a specific document store
updateDocumentStore 1 param body → 200404500
DELETE
/document-store/store/{id}
Delete a specific document store
deleteDocumentStore 1 param → 200404500
POST
/document-store/upsert/{id}
Upsert document to document store
upsertDocument 1 param body → 200400500
POST
/document-store/refresh/{id}
Re-process and upsert all documents in document store
refreshDocument 1 param body → 200400500
POST
/document-store/vectorstore/query
Retrieval query
queryVectorStore body → 200400500
DELETE
/document-store/loader/{storeId}/{loaderId}
Delete specific document loader and associated chunks from document store
deleteLoaderFromDocumentStore 2 params → 200400404500
DELETE
/document-store/vectorstore/{id}
Delete data from vector store
deleteVectorStoreFromStore 1 param → 200400404500
GET
/document-store/chunks/{storeId}/{loaderId}/{pageNo}
Get chunks from a specific document loader
getDocumentStoreFileChunks 3 params → 200404500
PUT
/document-store/chunks/{storeId}/{loaderId}/{chunkId}
Update a specific chunk
editDocumentStoreFileChunk 3 params body → 200404500
DELETE
/document-store/chunks/{storeId}/{loaderId}/{chunkId}
Delete a specific chunk from a document loader
deleteDocumentStoreFileChunk 3 params → 200400404500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are DocumentStoreLoaderForPreview (17 properties), DocumentStore (11 properties), DocumentStoreLoaderForUpsert (10 properties), DocumentStoreFileChunkPagedResponse (6 properties). Each schema is shown below with its type and property counts.

DocumentStoreLoaderFile
object
6 properties
DocumentStoreLoaderForRefresh
object
1 property
VectorUpsertResponse
object
5 properties
DocumentStoreLoaderForPreview
object
17 properties
DocumentStoreFileChunk
object
6 properties
DocumentStoreFileChunkPagedResponse
object
6 properties
DocumentStore
object
11 properties
Document
object
2 properties
DocumentStoreLoaderForUpsert
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flowise-document-store-api-openapi.yml Raw ↑

Other APIs Flowise publishes across the network.

Flowise assistants API
AE Profile APIs.io
Flowise attachments API
AE Profile APIs.io
Flowise chatflows API
AE Profile APIs.io
Flowise chatmessage API
AE Profile APIs.io
Flowise feedback API
AE Profile APIs.io
Flowise leads API
AE Profile APIs.io
Flowise ping API
AE Profile APIs.io
Flowise prediction API
AE Profile APIs.io
Flowise tools API
AE Profile APIs.io
Flowise upsert-history API
AE Profile APIs.io
Flowise variables API
AE Profile APIs.io
Flowise vector API
AE Profile APIs.io
#Document Store
← Back to F APIs
API Details
ID
flowise:flowise-document-store-api
Base URL
http://localhost:3000/api/v1
Docs
https://docs.flowiseai.com/api-reference
Provider
Flowise
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=flowise-document-store-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/flowise-document-store-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Flowise document-store API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.