Information
- License: AGPL-3.0-only
- OpenAPI version:
3.1.0
Overview
Yagra northbound API 0.2.1
Section titled “Yagra northbound API 0.2.1”The REST surface of Yagra-core: inventory, metrics, alerts, passive events and configuration.
This document is generated from the Rust handlers — it is the contract, not a description of one.
Operations
Section titled “Operations”DELETE
/api/v1/api-tokens/{id}DELETE
/api/v1/credentials/{id}DELETE
/api/v1/event-rules/{id}POST
/api/v1/llm/testPOST
/api/v1/rcaPOST
/api/v1/mutesDELETE
/api/v1/mutes/{id}DELETE
/api/v1/meraki/orgs/{id}DELETE
/api/v1/mib-catalog/{id}DELETE
/api/v1/pollers/{id}DELETE
/api/v1/node-groups/{id}POST
/api/v1/nodesDELETE
/api/v1/nodes/{node_id}GET
/healthzGET
/readyzPOST
/api/v1/profilesDELETE
/api/v1/profiles/{id}POST
/api/v1/usersDELETE
/api/v1/users/{id}DELETE
/api/v1/thresholds/{id}Authentication
Section titled “Authentication”bearer
Section titled “bearer”Either a session token from POST /api/v1/auth/login (short-lived; what the WebUI uses), or a personal access token (yat_…, Settings ▸ API tokens) whose surfaces include rest. A token issued for mcp only is refused here with 401. An API token acts as the account that owns it, so its role and its visibility scope are capped at that account’s current ones, and it stops working when the account is disabled or deleted; it cannot administer users, and endpoints that identify the signed-in account (/auth/me, the personal dashboard) answer 403 to it.
Security scheme type: http