Infrastructure
API
Make Infraova part of your own systems — authentication, endpoints, filtering, rate limits, and usage examples.
What the API is for
The Infraova API lets you pull infrastructure data, domain health, and operational records into your own systems and workflows. If you have internal dashboards, client reporting tools, or automation scripts, the API gives you programmatic access to everything Infraova monitors. The API is read-only — it does not expose endpoints for creating proposals or executing changes.
Authentication
The API uses API key authentication. Every request must include your API key in the Authorization header. API keys are created and managed from Settings → Organization → API Keys. Each key can be given a label to identify its purpose — one key for your internal dashboard, another for your reporting script.
Authorization: Bearer your_api_key_here
Base URL
All API requests are made to the base URL below. The API is versioned — the current version is v1. The version is included in the path.
https://api.infraova.com/v1
Core endpoints
The API exposes endpoints for the core data objects in Infraova. Domains returns the list of domains in your organization with their current health scores and status. Issues returns detected issues, filterable by domain, client, severity, and status. Clients returns your client list. Audit returns the operational history for a domain or your full organization.
GET /v1/domains GET /v1/domains/:id GET /v1/domains/:id/issues GET /v1/clients GET /v1/clients/:id/domains GET /v1/issues GET /v1/audit
Filtering and pagination
List endpoints support filtering via query parameters. You can filter issues by severity, status, domain, and client. Results are paginated — the default page size is 50 and the maximum is 100. Pagination uses cursor-based navigation. The response includes a next_cursor value that you pass as a parameter to retrieve the next page.
GET /v1/issues?severity=critical&status=open GET /v1/issues?domain_id=dom_abc123 GET /v1/domains?client_id=cli_xyz789&cursor=next_cursor_value
Rate limits
The API is rate limited to 120 requests per minute per API key. If you exceed the limit, requests return a 429 status with a Retry-After header indicating how many seconds to wait. For bulk data pulls, use filtering and pagination rather than making individual requests per domain.
Note
Rate limits are per API key, not per organization. If you need higher limits for a specific integration, create a dedicated key for that use case.
Response format
All responses are JSON. Successful responses return a data object containing the requested resource or array. Error responses return an error object with a code, message, and optional details field. HTTP status codes follow standard conventions — 200 for success, 400 for invalid requests, 401 for authentication failures, 404 for not found, 429 for rate limit exceeded.