Skip to main content
The Foveus API lets SDKs and services send telemetry to your workspace and retrieve observability data from the dashboard. Most teams do not need to call the API directly at first. Start with the .NET SDK:
The SDK handles authentication, batching, retries, capture, redaction, and ingestion.

When to use the API directly

Use the API directly when you need to:
  • build a custom SDK or integration
  • ingest telemetry from a platform Foveus does not support yet
  • automate workspace setup
  • query executions programmatically
  • connect Foveus data to internal tools
  • build custom operational workflows
For most .NET services, use the SDK instead.

Authentication

Foveus API requests use API keys. Test keys are created automatically during onboarding.
Live keys are not self-serve during private beta. They are issued by the Foveus team.
Keys are shown once. There is no API or dashboard control to rotate or revoke keys yet. Send the key from your backend service only.
Do not expose Foveus API keys in frontend JavaScript, mobile apps, public repositories, logs, screenshots, or client-side applications.

Modes

Foveus separates telemetry into two modes. The API key decides the mode: a fov_test_ key sends to Test mode and a fov_live_ key sends to Live mode. There is no separate mode setting.

Main API areas

The Foveus API is organized around telemetry and investigation workflows.

Ingestion API

The ingestion API receives telemetry from SDKs and integrations. It can include:
  • execution metadata
  • request context
  • response context
  • logs
  • metrics
  • exceptions
  • outcome evidence
  • custom context
For most services, the SDK sends ingestion data automatically. Ingestion is rate limited to 600 requests per minute per API key, for each telemetry type (logs, metrics, context and errors).

Executions API

The Executions API powers the Executions page. It can be used to query executions by:
  • service
  • status
  • method
  • endpoint
  • execution ID
  • trace ID
  • issue ID
  • duration
  • time range
  • indexed context fields
Example query shape:
Context search uses indexed context fields:
In the dashboard search bar, the same search is written as:

Issues API

The Issues API powers issue triage views. Issues represent observed recurring failure patterns. They are not confirmed root causes. An issue can include:
  • title
  • status: new, active, resolved or reopened
  • service
  • failure type: exception, http_error, timeout, business_rule, execution_error, dlq, retry_exhausted or sla_breach
  • hypothesis and suggested fix (rule-based text chosen by failure type and evidence)
  • common factors
  • occurrence counts
  • linked executions
  • lifecycle timestamps
  • assignment
  • comments and activity
Use issues when you want to understand recurring failure patterns. See Issues.

Logs API

The Logs API powers log exploration and execution-linked logs. Logs are most useful when correlated to executions. Use linked logs to inspect log lines for one request, job, or operation instead of searching through unrelated streams.

Service health API

GET /api/dashboard/services is a dashboard API. For a time window, it returns each service with its number of executions, the share that failed and the 95th percentile of execution duration. These figures come from executions, the same records the Executions page shows. Foveus does not offer metric time-series or trend charts; it is built for investigating executions.

Telemetry health API

GET /api/telemetry-health is a dashboard API. For a time window, it returns per service whether telemetry is complete, delayed, possibly incomplete or incomplete. Foveus derives this from the telemetry loss it records: requests rejected by the ingestion rate limit, items the SDK reports it dropped, SDK retries and pauses, and items Foveus received but could not store. Use it to tell missing data apart from no activity. The dashboard shows the same status as a banner.

Context search API

Execution Context Search lets you find executions by indexed business context. Example dashboard query:
Equivalent API shape:
String values should be quoted in the dashboard query language:
When calling the API directly, URL-encode values where needed.

Pagination

List endpoints use pagination. Common parameters include: Example:

Error responses

Foveus APIs return structured errors. Common error types may include: Error names may evolve during private beta.

Rate limits and guardrails

Foveus applies guardrails to protect workspace performance and ingestion reliability. These can include:
  • API key rate limits (600 ingestion requests per minute per key, per telemetry type)
  • request size limits
  • context indexing limits
  • maximum page size
  • maximum context keys per request
  • maximum values per key
  • time-window limits for broad context searches
These limits help keep searches predictable and safe.

Private beta note

The public API reference is still evolving during private beta. Use the SDK where possible. If you need direct API access, confirm the current endpoint contract with the Foveus team before building production workflows against it.

What to do next