Watching the calls
Weik.io 2026.2Follow the calls to an API, and find one call by the traceresponse header of its response. Product page · Video
Watch: Watch the calls, 3:33
The video finds each call on the Requests page and follows one of them into its trace.
This part of the video couldn't be loaded.
On this page
You see the calls to an API on the API’s page in the admin UI and with the CLI. A failure is on the server’s side when the gateway or the system behind it failed. It’s on the caller’s side when the cause was in the call:
- A missing or unknown credential
- A subscription that doesn’t open the API, or has expired
- A rate limit
- A malformed request
The Requests page#
Open Requests under Observability on the API’s page to see one row per call. Each row shows the call’s status and what happened. You can filter the rows by the call’s details:
- Version
- Subscription
- Route
- Status
- Side that failed
- Response time, slower than a time you set
Open a row to see the call’s trace through the gateway and into the integration behind it.




The figures#
Open the API’s Overview to see the figures for the last day:
- The number of calls
- The share of calls that failed on the server’s side
- The share of calls that failed on the callers’ side
- The response time
- The part of the response time spent in the integration behind the API
The Overview also shows the current requests a second.
In Metrics, you choose what to break the calls down by:
- Status code
- Version
- Route
- Subscription
To decide when an old version can be retired, open the Versions tab and check how many calls and failures each version had and when it was last called. To find a declared route that had no calls, open the Routes tab.
weikio metrics shows the same breakdowns:
$ weikio metrics --api finance/invoices --env production --by status
$ weikio metrics --api finance/invoices@v1 --env production --by subscriptionFind one call#
The gateway’s responses carry a traceresponse header. Ask a caller who reports a failed call for that header’s value:
$ curl -i -H "X-Api-Key: $PARTNER_KEY" https://api.example.com/invoices/v1/pendingPaste the value into the search of Observability › Traces, or pass it to weikio trace:
$ weikio trace 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01The trace shows the route the call matched at the gateway and the integration behind it. On Camel 4.18.5 the trace shows each step of the integration, and on 4.22.1 only the integration’s run and the calls it makes. A trace that crosses into a project you can’t read shows the steps you may see and says how many it hides.
Logs of the gateway#
To read the gateway’s log lines for an API in one environment, open the API’s Logs section. To find the gateway’s lines among the others in Observability › Logs, filter by API and look for APIM instance in the Runs on column.
When an API fails#
Weik.io raises a problem when at least 5 % of at least 20 calls to an API version in one environment fail on the server’s side in 15 minutes. From 25 % it’s an error. The problem shows its figures, such as 42 of 310 calls failed on the server side in 15 min. You see it in the admin UI and the CLI:
- Needs attention on Home
- The Observability Overview
- The API’s page
weikio problems
How long traces are kept#
Weik.io keeps a call’s trace for 7 days by default, or less once the trace store reaches its disk cap. To change the days, run weikio settings set --traces-retention.
To trace only a share of the calls on a busy installation, set WEIKIO_APIM_TRACE_SAMPLE_RATIO in the hub’s .env.