Customer health
Explainable health scores combine reliability, activity, latency, endpoint adoption and usage regularity.
Prioritize accounts before they escalate.API analytics for B2B software
Apirelio turns API requests into customer health, endpoint usage, error, version and release analytics — without capturing payloads.
/v2/invoices/{invoice}/send422From telemetry to decisions
Apirelio turns API traffic into a shared operating view for engineering, support and customer success.
Explainable health scores combine reliability, activity, latency, endpoint adoption and usage regularity.
Prioritize accounts before they escalate.Compare every release with its preceding baseline and find regressing endpoints and affected customers.
Connect deploys to customer outcomes.Track first request, first success, production adoption, time-to-value and stalled implementations.
Make onboarding measurable.Measure traffic share by API version and identify the exact customers that still need migration.
Retire legacy contracts with confidence.Get a deterministic comparison of traffic, errors, latency, endpoints and customer movement.
No opaque AI summary required.Detect inactivity, error-rate spikes and traffic drops, then deliver scheduled stakeholder summaries.
Keep the right people informed.Framework-native setup
Add the Laravel, Symfony or Nette package and configure your project ingestion key.
Resolve each authenticated request to its B2B customer and consuming application.
Open the dashboards, investigate regressions and automate alerts and reports.
Developer documentation
Choose your PHP framework, follow its quickstart and review the shared privacy-safe event model.
Trust is part of the product
Apirelio separates operational analytics from sensitive application data. Project-scoped keys, bounded metadata and configurable retention keep the data surface intentionally small.
Request bodies, response bodies, credentials, cookies and query strings stay out.
Ingestion keys belong to one project, are stored as hashes and can be revoked.
Telemetry delivery runs away from the customer response path and never changes it.
Retention, captured fields and current security posture are documented clearly.