User guide

1. 1

   Connect your app

   An admin creates a project under Projects and allows the address where the app runs (its origin). A developer adds the setup code from the project page and connects axios if the app uses it.

2. 2

   Try a real task

   Open your monitored app, visit a list, search, filter and open a record’s details. Data accumulates only for the flows you exercise.

3. 3

   Choose the project and time range

   Select your project on the left. On data screens, use range in the top bar to choose a time period. Start at Overview, then open an endpoint from Findings.

4. 4

   Improve, then repeat the task

   After your developer makes a change, repeat the same flow. Choose a time range covering the new attempt and review duration, size and findings, taking care not to mix in older measurements.

Viewers can read data. Developers can act on findings. Project, member and integration settings require an admin or owner.

In the workspace, Organization manages the team space and Members manages access roles. Audit log shows authorized members who changed what. Your account menu provides language, theme and personal settings.

1. 1. Choose a finding

   Start with high-priority findings. Open its endpoint and inspect the recorded evidence before assigning work.

   Open findings

2. 2. Review the evidence

   Use the endpoint’s Fields section to see observed reads and their pages, scenarios and call sites. Missing or unknown tracking does not prove a field is unused.

   Open endpoints

3. 3. Create a Papyro card

   Use the endpoint’s Actions section to create a Papyro card when connected. Keep task assignment and delivery status in Papyro; Apiheron notes support the technical investigation.

   Open findings

4. 4. Verify the fix

   Open Verify fix on the same endpoint. Compare baseline and current releases using equivalent interactions. Without sufficient captures the screen explains what is missing. New high-severity findings and regressions appear as a compact overview summary.

   Choose an endpoint

window.apiheron.startScenario("checkout");

window.apiheron.endScenario();

API

The way an app asks a server for information or an action. Think of a restaurant’s ordering channel.

Endpoint

The address for a particular job, such as /api/products for products. Calls to that address are examined together.

Request and response

“Get the products” is a request; the returned product information is the response. Reopening a page may create another request.

Field

One piece of information in a response: product name, price or stock. Apiheron tracks whether code reads it.

Session

A browser activity group used by the SDK. Session counts help you understand how many separate uses support an observation; they are not a person count.

Duration · p50 · p95

Duration is the time from a browser request starting until its response downloads. 1,000 ms = 1 second. Half of requests finish within p50; 95% finish within p95.

Response size

The uncompressed size of returned JSON. A larger package means more data; compression may make the actual network transfer smaller.

Error rate

The share of requests returning error status codes. An expired login or missing record can be a cause; check the status code in the details.