Grafana HTTP API infrastructure boundary

Evidence-backed facts

1. Grafana documents HTTP APIs for dashboards, folders, data sources, alerting, annotations, service accounts, organizations, users, and other resources. informative
2. GET and search requests are distinct from POST, PUT, PATCH, DELETE, provisioning, alert changes, and administrative operations. informative
3. Basic authentication, service-account tokens, role and resource permissions, organization scope, edition, and version determine allowed operations. informative
4. API documentation does not prove an endpoint is enabled, a token is authorized, data-source results are correct, a write succeeded, or Grafana is deployed. informative

Primary sources