Stats overview

What the Stats API does, prerequisites, quick start, common use cases, and errors.

Overview

The Stats API returns your own organization's API usage — every call your applications made against Samtec's APIs, rolled up into daily summaries or broken down to the individual request. Use it to monitor call volume and response times, or to pull the exact request and response for one specific call when you're debugging something that went wrong.

Stats are scoped to your organization only — you'll never see another customer's traffic. There's no way to query someone else's usage even if you know their trace identifiers.

Prerequisites

Every request needs the standard Authorization: Bearer <token> and client-app-name headers described in Authentication. Rate limits are the same as every other API on this portal: 1,000 requests per second.

Quick start

Get a rolled-up summary of your organization's usage for the last 7 days:

curl https://api.samtec.com/stats/v1/requests/summary \
  -H "Authorization: Bearer YOUR_JWT_TOKEN" \
  -H "client-app-name: your-app-name"

[
  {
    "Api": "catalog",
    "RequestDate": "2026-08-27",
    "Action": "GET /v3/{part}",
    "AverageResponseTimeMs": 118,
    "RequestCount": 4820
  }
]

Common use cases

Track call volume and latency over time. /v1/requests/summary gives you a 7-day rolling view of request counts and average response time, grouped by API and action — useful for spotting a spike in traffic or a slowdown before it becomes a support ticket.
List the requests you made against a specific API on a specific day. /v1/requests/details?api=catalog&date=2026-08-27 returns one row per call, including its response code and trace identifier.
Debug a specific failed or unexpected call. Once you have a TraceIdentifier from /v1/requests/details, /v1/requests/fulldetail returns the exact request and response body Samtec logged for that one call.

One thing worth knowing: the api parameter on /v1/requests/details and /v1/requests/fulldetail uses each API's internal name, not always the name you see elsewhere on this portal — catalog, orders, pricing, and quotes match, but Lead Time's internal name is delivery. [ TODO: confirm with API owner ] whether Models or Stats calls themselves show up under either of these endpoints, or under some other internal name.

Common errors

Status	Meaning	How to resolve
400	Missing or malformed header (often a missing `client-app-name`)	Check both required headers are present.
401	Missing or invalid JWT	Confirm the `Authorization` header is `Bearer <token>`.
429	Rate limit exceeded (1,000 req/s)	Retry with backoff.
500	The query against the underlying stats store failed	`[ TODO: confirm with API owner ]` — the source returns a generic 500 for any query failure, including a malformed `date` value; retry with a well-formed `date` (`yyyy-MM-dd`) first before treating this as a service issue.

All APIs on this portal. Stats reports your usage across every API you call — Catalog, Lead Time, Pricing, Orders, Quotes, and Models — not just one of them.

What's next?

Stats Reference — every endpoint, its parameters, and a live playground.
Catalog — see usage on the API most consumers start with.
Orders — check your order-placement volume alongside your read traffic.