Skip to main content
Endpoints → Analytics is your hub for understanding project performance and usage. It shows response times, request volume, endpoint trends, and detailed logs for every call.

​
Project statistics

Uniblock Analytics provides the following data for your project:
  • Average latency — average API response time; lower is better for user experience
  • Successful requests — count of completed requests
  • Failed requests — count of requests that returned an error or did not complete
  • Total requests — cumulative request count for activity and usage patterns
  • Endpoint calls over time — chart of successful, failed, and total requests over time

​
API key analytics

In addition to project-wide analytics, Uniblock provides the same metrics broken down per API key: average response time, failed requests, total requests, and total usage. Use this to spot anomalies tied to a specific key or environment (for example, a staging key spiking in errors while production stays clean).

​
API logs

Scroll to See Detailed Logs at the bottom of the Analytics tab for a per-request table showing: method, endpoint, status code, provider used, response time, and timestamp.

​
Why logs matter

API logs show how your application behaves in production. Use them to:
  • Identify and diagnose issues as they happen
  • Monitor API health and response-time trends
  • Track request patterns across endpoints
  • Detect unexpected or suspicious activity

​
Reading the logs table

Each row in the logs table summarizes one outbound call, including any provider fallback attempts that occurred:
  • Method — HTTP method (GET or POST)
  • Endpoint — API endpoint accessed (e.g. /v1/token/metadata)
  • Status — success or error status code
  • Provider — provider that returned the final response
  • Response — provider response(s) attempted for the call (multiple when fallback routing fired)
  • Response time — end-to-end latency for the request
  • Date — exact timestamp when the request was made

​
Detailed request logs

Click any log row to expand the full request detail, which includes every fallback attempt across providers:
  • HTTP method — e.g. GET
  • Endpoint name — e.g. TokenMetadata
  • Endpoint path — e.g. /v1/token/metadata
  • Timestamp — exact request time
  • Response time — server processing duration
  • Headers — request metadata (Host, User-Agent, Accept, and others)
  • Query parameters — additional request context
  • Request body — payload for POST or PUT requests
  • Response headers & body — provider response data (multiple entries appear when fallback routing was used)

​
Filtering and searching

Use the filter controls at the top of the logs table to narrow by provider, status code, endpoint, or time range. The search bar matches keywords or error messages across all log fields.

Ready to get started with Uniblock?

Create your free account and start building with unified blockchain infrastructure across 100+ chains.

View API reference

Explore all available endpoints and interactive playgrounds