Aapirelio

Customer integration intelligence

Every API request tells a customer story.

Apirelio connects telemetry, customer identity and release context so your teams can see risk, adoption and impact in one place.

Create your workspace →Read the docs
Billing API · ProductionLive
Health score84+6 pts
Active customers483 at risk
Success rate98.7%+0.4%
Customer trafficLast 7 days
124.8k requests
release 2.4.0
!
Release regression detectedPOST /invoices/send · +38% latency
now
Pre-release impact Customer-aware telemetry OpenAPI intelligence Privacy by default
Flagship intelligence

API change impact simulator

Know the blast radius before the breaking change ships.

Upload the OpenAPI contract proposed for your next release. Apirelio compares it with the current contract, then maps every risky change to real production traffic and the exact customers who depend on it.

  • ✓ Removed operations, required parameters and auth changes
  • ✓ Affected customers and percentage of production traffic
  • ✓ Evidence-backed pre-release verdict without payload capture
Analyze your next API change →
Current contractBilling API v2.442 operations
→
Candidate contractBilling API v3.039 operations
Analyzed
!
Pre-release verdict8 customers are in the blast radius23.4% of observed production traffic

3breaking changes

!

Operation removedPOST /v1/invoices/{invoice}/send

1,240 requests
6 customers
!

New required parameterPOST /v2/refunds

842 requests
4 customers
△

Authentication changedGET /v2/customers/{id}

381 requests
2 customers
AENSLCOS

Acme Europe is most exposed2 breaking changes · 628 requests

Review customer →
01

Customer health

Know who needs attention before the support ticket arrives.

One explainable score combines usage, reliability, latency, endpoint adoption and regularity. Every score includes the signals and components behind it.

  • ✓ Portfolio view across every customer
  • ✓ Healthy, warning, critical and inactive states
  • ✓ Traffic movement against the previous period
Customer healthAcme Europe
Healthy
90Health score
Activity30/30
Reliability26/30
Performance14/15
Adoption12/15
Regularity8/10
Traffic +18%vs previous 7 days
1.2% error ratewithin target
4 endpoints1 not yet adopted
02

Release impact

Connect every deployment to the customers it affected.

Compare a release with its preceding equal-duration baseline. See whether success rate or latency regressed, which endpoints moved and who experienced the change.

  • ✓ Automatic before-and-after baseline
  • ✓ Endpoint-level regression ranking
  • ✓ Exact list of affected customers
Release impact2026.07.29.1
Regression
Baseline98.4%141 ms P95
−13.8%→+118% latency
Current release84.6%308 ms P95
EndpointRequestsError change
POST /invoices1,248+8.4%
POST /invoices/{id}/send918+4.2%
GET /customers/{id}2,841stable
Example incident

From signal to action

One risky release. Four affected customers. No guesswork.

An illustrative workflow using the same signals available in the Apirelio demo workspace.

Release2026.07.29.1Production
Observed impactSuccess −13.8 ptsLatency +118%
AENSOSLC
4 customers affectedLumen Commerce is most impacted
  1. 10:04
    DeployRelease 2026.07.29.1 starts serving traffic

    Release context arrives automatically with request telemetry.

  2. 10:12
    DetectPOST /invoices begins regressing

    Error rate rises and P95 latency moves from 141 ms to 308 ms.

  3. 10:13
    ScopeFour affected customers identified

    Engineering sees the endpoint; Support and Success see the accounts.

  4. 10:20
    ActThe team has one shared incident picture

    No payload search, log correlation or customer-ID translation required.

OutcomeFrom deployment to customer impact in one investigation path.Explore the demo →
03

Integration journey

Turn onboarding into a measurable funnel.

Track every account from its first connection to regular production usage. Surface stalled integrations with the next action needed to move forward.

0148Connected→
0243First success→
0339Production→
0434Adopted→
0531Regular
LC
Lumen CommerceConnected 2 days ago · 2 failed requests
Stalled

Next best actionResolve the first failing request

One shared operating view

Answer the questions that generic observability cannot.

API version adoption

Who is still on v1?

Track traffic share and get a customer migration list.

86%on v2
v2 · 43 customersv1 · 7 customers
What changed?

A deterministic daily briefing.

Compare traffic, reliability, latency, customers and errors.

Requests+18.4%vs prior period
Error rate+2.1 ptsneeds attention
New errors3codes detected
Alerts and reports

Keep every team ahead of risk.

Monitor inactivity, high error rates and traffic drops, then send scheduled summaries.

Orbit Systems error rate18.7% in the last hourOpen
Acme Europe traffic drop42% below previous periodOpen
Daily integration reportDelivered to 3 recipientsSent

Built for your team

One source of truth. Different decisions.

Every team sees the same integration reality through the lens of the work they need to do.

Engineering

Ship changes without losing customer context.

Connect deploys to reliability, latency and the exact accounts affected by a regression.

  • ✓Release impact
  • ✓Endpoint regressions
  • ✓Error diagnostics
Billing APILast 7 days
P95 after release308 ms+118%
CustomerAcme Europe
EndpointPOST /invoices/send
Release2026.07.29.1

Trust by design

Useful insight without risky data collection.

Apirelio collects operational integration signals, not application payloads. The SDK is designed to fail independently from the API it observes.

◇

Privacy first

No bodies, credentials, cookies, query strings or IP addresses.

↗

Fail-safe SDK

Network delivery runs outside the customer request and failures never change its response.

⌁

Framework native

Normalized routes and customer resolvers for Laravel middleware, Symfony kernel events and the Nette application lifecycle.

◎

Real-time ingestion

ClickHouse-backed analytics designed for high-volume request telemetry.

Your Laravel API
POST/invoices/{invoice}/send
Middleware observes outcome and context
Async batch→
Apirelio event
customer_idroutestatusduration_msrelease
Project-scoped ingestion key
CapturedOperational signals only

Normalized route, status, duration, customer and application IDs, API version, release and allow-listed metadata.

Never capturedSensitive request data
Request bodiesResponse bodiesCredentialsCookiesQuery stringsIP addresses
ControlsBounded and revocable

Keys are project-scoped and revocable, stored as hashes, metadata is allow-listed and retention is configured per project.

Coming next

The intelligence layer keeps growing.

These capabilities build naturally on the telemetry and customer context already in Apirelio.

Next

Automatic API version resolvers

Infer versions from route prefixes or custom application logic.

Live

Symfony SDK

Messenger-backed, fail-safe instrumentation for Symfony 6.4 through 8.x.

Live

Nette SDK

Native DI extension and fail-safe lifecycle instrumentation for Nette 3.2 and 3.3.

Planned

OpenTelemetry bridge

Connect integration context with existing observability stacks.

Exploring

AI-assisted investigation

Turn deterministic signals into suggested causes and next actions.

See your integrations clearly

Find the risk hiding inside your API traffic.

Start monitoring →Open demo dashboard