Chat API
The Chat API is where every integration starts. It signs users in and issues the access token that the other VDF AI APIs accept, and it holds the conversational layer of the platform: chat sessions and their messages, the documents people upload, and user profiles.
It is also where third-party systems are connected. Integrations such as Jira, Confluence, GitHub, and Microsoft 365 are authorised and synchronised here, and their content is indexed into the knowledge your agents search. Network triggers, which start a network when something happens in a connected system, live here too.
Administrators use the Chat API to run the deployment: users and groups, directory synchronisation and single sign-on, backups, company details, platform settings, and licence usage.
Resources
Sign in for an access token, read the current session, and start Microsoft sign-in.
List your conversation sessions, read their messages, and rename or delete them.
Upload files to your document library, list them, extract their text, download, and delete.
Read and update the signed-in user's own profile, password, avatar, and company details.
Rules that let an incoming email or Teams message start a network run automatically.
Connect, disconnect, and sync the systems a deployment reads from, using one uniform contract per provider.
Connect Jira, browse projects, boards and issues, create and update issues, and manage event webhooks.
Connect Confluence, browse spaces and pages, search content, and create or update pages.
Connect a GitHub account with a personal access token and list the repositories it can reach.
Build and check the per-integration search indexes that agent search tools read.
AdministrationEndpoints for the administrators of your deployment.
Create, list, update and deactivate the user accounts of your deployment, one at a time or in bulk.
Manage permission groups, the named sets of users that resources can be shared with, and their members.
Browse Microsoft Entra ID users and groups, import them, and keep linked permission groups in step with the directory.
Map Microsoft Entra ID security groups to roles for single sign-on, and check that sign-on is fully configured.
Create, list, download, restore, and delete full backups of the platform database and stored files.
Read and update the organisation's company profile and billing details.
Read and change the Chat service's runtime settings, and read its recent error and warning log entries.
Report the platform's metered usage against its licence, by month, day, service, user, and event.
OperationsHealth checks for monitoring and load balancers.
Liveness probes that report whether the Chat service is running.