yggy support
Overview
yggy API v1
Section titled “yggy API v1”The yggy REST API. Every operation here accepts a personal or organization API key, in the x-api-key header or as Authorization: Bearer <key>. Send one credential per request. Actions that only a person signed in to the yggy app may take, such as creating API keys or deleting an account, are not listed. Tokens from an MCP sign-in work on the MCP server only, not on these operations.
Information
- Terms of Service
- License: Apache-2.0
- OpenAPI version:
3.1.0
Operations
Section titled “ Operations ”DELETE
/api/v1/chat/sessions/{id} POST
/api/v1/chat POST
/api/v1/chat/stream DELETE
/api/v1/connections/{id} DELETE
/api/v1/documents/{id} PATCH
/api/v1/documents/{id} DELETE
/api/v1/documents/{id}/purge DELETE
/api/v1/graph/triples/{id} GET
/api/v1/projects POST
/api/v1/projects DELETE
/api/v1/projects/{projectId} POST
/api/v1/providers POST
/api/v1/query GET
/api/v1/rooms POST
/api/v1/rooms DELETE
/api/v1/rooms/{roomId} PATCH
/api/v1/rooms/{roomId} POST
/api/v1/saga/ask PATCH
/api/v1/saga/notes/{id} POST
/api/v1/saga/links Authentication
Section titled “ Authentication ”bearerAuth
Section titled “bearerAuth ”The same API key sent as Authorization: Bearer <key>.
Security scheme type: http
apiKeyAuth
Section titled “apiKeyAuth ”A personal (ygg_) or organization (ygg_org_) API key from Developers → API keys, sent in the x-api-key header.
Security scheme type: apiKey
Header parameter name: x-api-key