Atatus API

Name: Atatus API API
Brand: Atatus API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey11 EndpointsREST

For Agents

Pull pages, errors, transactions, ajax calls, and web vitals from an Atatus project to feed dashboards, alerts, or AI incident summaries.

Quickstart

Get started with Atatus API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list top errors for an Atatus project"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Atatus API API.

List monitored pages for a project and drill into a single page by id via /projects/{projectId}/pages

Retrieve error events captured by the Atatus agents through /projects/{projectId}/errors

Inspect ajax call performance and routes seen by the browser agent

Read transaction-level performance for back-end services using /projects/{projectId}/transactions

GET STARTED

Start building with Atatus API API

Explore with Jentic

View OpenAPI Document

Use for: List the slowest transactions for a project over the last hour, Retrieve the top errors for a project today, Get Core Web Vitals for a marketing site project, Find the route with the highest error rate in a project

Not supported: Does not handle agent installation, alerting rules, or user management — use for reading captured monitoring data (errors, transactions, routes, web vitals) only.

The Atatus API exposes performance and error monitoring data captured by the Atatus application, browser, and infrastructure agents. It is project-scoped: every endpoint takes a project id and returns the pages, ajax calls, routes, transactions, errors, web vitals, or report rollups associated with that project. The surface is read-oriented — useful for piping monitoring data into dashboards, reliability reviews, and AI-driven incident summaries rather than configuring the monitoring agents themselves.

Use Cases

Patterns agents use Atatus API API for, with concrete tasks.

★ Reliability Dashboard Backfill

SRE teams build internal dashboards that combine APM data with deploy and incident metadata. The Atatus API's project-scoped endpoints (/transactions, /errors, /routes, /webvitals) let an ingestion agent backfill a metrics store for each project, on a schedule, without exporting from the Atatus UI. The result is a unified reliability view across services that already report into Atatus.

For project id 'acme-prod', list errors and slowest transactions for the last 24 hours and write them to the reliability data warehouse

AI-Generated Incident Summary

When an incident hits, on-call engineers want a one-paragraph summary of what's happening across pages, routes, and transactions. An LLM agent calls /projects/{projectId}/errors and /projects/{projectId}/transactions for the affected window, then summarises the top failing routes and slow transactions for the incident channel. Time-to-first-summary moves from a manual dig to under a minute.

Fetch the last 30 minutes of errors and slowest transactions for project 'acme-prod' and produce a 5-bullet incident summary

Web Vitals Tracking for Marketing

Marketing and front-end teams want to track Core Web Vitals for the public-facing site over time, separate from APM. The /projects/{projectId}/webvitals endpoint returns LCP, FID, and CLS for the project, so a tracking agent can record weekly snapshots and flag regressions tied to releases. This keeps SEO-relevant performance metrics under continuous review.

Pull /projects/{projectId}/webvitals for the marketing-site project and alert if LCP exceeds 2.5 seconds

Atatus Insights Through Jentic

Through Jentic, an AI agent answering an APM question searches by intent ('show me top errors today') and Jentic returns the matching Atatus operation with its project-id parameter. The X-API-KEY credential is held in the Jentic vault, so the agent never sees the secret. This makes monitoring data answerable directly in any LLM chat or ops workflow.

Use Jentic to search 'list top errors for project today', load GET /projects/{projectId}/errors, and execute with the active project id

Key Endpoints

11 endpoints — the atatus api exposes performance and error monitoring data captured by the atatus application, browser, and infrastructure agents.

METHOD

PATH

DESCRIPTION

GET

/projects/{projectId}/pages

List monitored pages for a project

GET

/projects/{projectId}/errors

List error events for a project

GET

/projects/{projectId}/transactions

List transactions for a project

GET

/projects/{projectId}/routes

List back-end routes for a project

GET

/projects/{projectId}/ajax

List ajax calls for a project

GET

/projects/{projectId}/webvitals

Get Core Web Vitals for a project

GET

/projects/{projectId}/pages

List monitored pages for a project

GET

/projects/{projectId}/errors

List error events for a project

GET

/projects/{projectId}/transactions

List transactions for a project

GET

/projects/{projectId}/routes

List back-end routes for a project

GET

/projects/{projectId}/ajax

List ajax calls for a project

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Atatus X-API-KEY values are stored encrypted in the Jentic vault (MAXsystem). Jentic sets the X-API-KEY header at call time, so the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list top errors for a project') and Jentic returns the matching Atatus operation with its project-id parameter, so the agent calls the right /projects/{projectId}/* endpoint directly.

Time to first call

Direct integration: half a day to wire X-API-KEY auth and project-scoped queries. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

New Relic

Full-stack observability platform with APM and infrastructure

Choose New Relic when the deployment already standardises on New Relic for APM and logs

Alternative

Sentry

Error-tracking and performance monitoring platform

Choose Sentry when the focus is application errors and release health rather than RUM and web vitals

Alternative

Raygun

Crash and APM platform with real user monitoring

Choose Raygun when the team needs crash reporting and RUM bundled together

FAQs

Specific to using Atatus API API through Jentic.

What authentication does the Atatus API use?

The Atatus API uses an API key in the X-API-KEY header. Through Jentic, the key is held in the encrypted vault and the header is set at call time, so the secret never enters the agent's context.

Can I list errors for a specific Atatus project?

Yes. GET /projects/{projectId}/errors returns the captured error events for the given project, and GET /projects/{projectId}/errors/{errorId} returns the detail for a single error. Combine them to build an error-triage workflow scoped to the project.

What are the rate limits for the Atatus API?

The spec does not encode an explicit rate limit. Atatus throttles per workspace API key, so the safe pattern is to back off on HTTP 429 responses and prefer batched range queries over polling per id.

How do I get Core Web Vitals for a project through Jentic?

Search Jentic for 'get core web vitals for a project', load GET /projects/{projectId}/webvitals, and execute with the project id. Jentic injects the X-API-KEY and validates the project-id parameter before the request is sent.

Can I retrieve transactions by id with the Atatus API?

Yes. GET /projects/{projectId}/transactions lists transactions for a project, and GET /projects/{projectId}/transactions/{transactionId} returns the single-transaction detail used for drill-downs in incident reviews.

Does the Atatus API support configuring the monitoring agents?

No. The API surface is read-oriented around captured monitoring data — pages, ajax, routes, errors, transactions, web vitals, and reports. Agent configuration still lives in the Atatus dashboard.