yams/docs/api
2025-12-22 14:18:31 -05:00
..
examples/storage_plugin build system improvements, clang-tidy integration for warnings equals errors (need to continue). POSIX socket legacy code removal 2025-09-03 13:22:30 -04:00
graph_adapter_v1.md stagging v0.7.0 2025-09-25 16:40:56 -04:00
mcp_tools.md completing test migration, mcp tool consolidation, prompt updates 2025-12-22 14:18:31 -05:00
README.md v0.7.3 staging 2025-10-07 11:18:35 -04:00
storage_plugin_v1.md build system improvements, clang-tidy integration for warnings equals errors (need to continue). POSIX socket legacy code removal 2025-09-03 13:22:30 -04:00

YAMS API Documentation

A concise index for YAMS HTTP API docs. Start here, open the spec, and generate a client if you need one.

What’s here

If you’re exploring or automating against YAMS via HTTP, read the guides and treat openapi.yaml as the source of truth.

TL;DR

  • View the API quickly:
    • Drag-and-drop openapi.yaml into https://editor.swagger.io/
    • Or use Redocly locally (if installed): redocly preview-docs docs/api/openapi.yaml
  • Generate a client (examples):
    • With openapi-generator (Homebrew):
      brew install openapi-generator
    • TypeScript (fetch):
      openapi-generator generate -i docs/api/openapi.yaml -g typescript-fetch -o ./api-clients/ts
    • Python (requests):
      openapi-generator generate -i docs/api/openapi.yaml -g python -o ./api-clients/python
    • C++ (cpp-httplib, experimental):
      openapi-generator generate -i docs/api/openapi.yaml -g cpp-httplib -o ./api-clients/cpp
  • Base URL:
    • During development, the HTTP server (if enabled) typically runs on localhost. Check your server configuration for the exact host/port.
  • Auth:
    • See the “security”/“components.securitySchemes” section in openapi.yaml for the current scheme(s).

Quick usage patterns

  • cURL shape (consult endpoint/params in the spec or topical guides):
    • GET with query params:
      curl -sS "<BASE_URL>/api/v1/<resource>?q=..." | jq
    • POST with JSON body:
      curl -sS -X POST "<BASE_URL>/api/v1/<resource>" -H "Content-Type: application/json" -d @payload.json | jq
    • Auth header (if required):
      -H "Authorization: Bearer <TOKEN>" or -H "X-API-Key: <KEY>" (see spec)

For concrete examples, see:

Development notes

  • The HTTP API surface may evolve with releases; openapi.yaml in your branch/tag matches that build.
  • If you don’t see a running HTTP server, use:
    • CLI: docs/user_guide/cli.md
    • MCP server (for AI tools/workflows): docs/user_guide/mcp.md

See also

  • CLI Reference: ../user_guide/cli.md
  • Installation: ../user_guide/installation.md
  • Troubleshooting search: ../troubleshooting/search_issues.md

This page is an index stub intended to be brief and link-rich. For authoritative details, rely on the OpenAPI spec and topical guides.