Skip to main content

Knowledge base

These endpoints search and manage your knowledge base: the Library documents your team uploads or imports (manuals, SOPs, method statements, supplier documents), plus the customer and account summaries VH3 AI builds from your job history. Search looks at each document’s title, summary and contents. Where page-level search is switched on for your company, it also matches what is written on each page, so a model number, fault code, part number or procedure step finds the right page even when the summary does not mention it. Results never include page text. Every result is checked against the document’s current sharing settings before it is returned. A document that was deleted, or made private, drops out of results straight away. Base URL: https://api.vh3connect.io/api:kP8T1CK7 Send company_id and api_key in every request, as with the rest of the VH3 AI API. Keep the API key in server-side code.
Private documents. Library documents are either shared with the whole company or private to one user. Searches return shared documents only, unless you pass acting_user_id: then that user’s private documents are included too. acting_user_id must be a user in your company.

POST /knowledge/documents/search

Find Library documents, and their best matching pages, that answer a question. Request body:
Response:
When the same document has been uploaded more than once, page-level results show one copy: the copy with the best match.

POST /knowledge/search

Search across Library documents and customer and account intelligence in one call. Use it for questions either could answer, such as “which customers have a history of door entry faults” or “what does our method statement say about lone working”. Request body:
Response:

POST /knowledge/documents/upload

Upload one PDF to your Library. The document goes through the same processing as an upload in VH3 Connect: text extraction, a summary, a page-by-page guide, and indexing for search. Send the request as multipart/form-data. Form fields:
Response:
The response returns as soon as the file is stored and read. status is processing while the summary, page guide and search index finish, then ready. Short documents are usually searchable within a minute.
Uploading the identical file again within an hour returns the first upload’s result instead of adding a second copy.
Errors: 403 for an invalid API key or a user_id outside your company; 400 for a file over 100 MB or 150 pages.

POST /knowledge/documents/share

Share a Library document with the whole company, or make it private to its owner again. Request body:
Response: { "documentId": "…", "shared": true }. Search results reflect the change straight away.

POST /knowledge/documents/delete

Delete a Library document. The file is removed, and the document stops appearing in search, Connie and Tia straight away. Request body:
Response: { "deleted": true, "documentId": "…" } Errors (share and delete): 403 for an invalid API key; 404 when the document doesn’t exist, isn’t in your company, or isn’t owned by user_id. Deleting can’t be undone.

From a front end

For a browser or mobile app with no back end of its own, use the signed-in user versions instead. They take a JWT from User Authentication (JWT) and never an API key, and they run as the signed-in user. Base URL: https://api.vh3connect.io/api:uCamsOiN
Responses match the API-key endpoints above.

Connie and the knowledge base

Connie can answer from your knowledge base too. When page-level search is on for your company, Connie searches the Library, reads the pages that match, and gives a page citation for each statement, for example [Vaillant ecoTEC Manual.pdf, p. 13]. She can also list the newest documents and, when a user asks, import a file from their own connected Google Drive into the Library. See Connie and Knowledge base in VH3 Connect.