Skip to content
Docs
Follow yggy on LinkedInFollow @yggy_tech on X

Request logs

Developers → Usage and logs shows the requests your organization’s API keys and connected apps (MCP clients) make. Use it to find out why a call failed without digging through your own logs.

What you see

Section titled “What you see”
  • Totals for the last 24 hours or the last 7 days: requests, error rate, p95 latency and rate-limited requests, with a chart per hour or per day.
  • The requests, newest first. Each row shows the time, the method and route, the status, the response time, the key or app that made it and, for admins, the member. Load more shows older rows.
  • Filters for the credential, the status class and the route.
  • Select a row to see its request ID, the client IP and the error code, with a hint for fixing a failed call.

For an MCP request, the row also shows the tool it called. When one request sends several MCP calls at once, the log keeps the first one.

What is logged

Section titled “What is logged”
  • Every request made with a valid API key or app token in your organization, including requests that failed or were rate limited.
  • For each request: the time, the method, the route it matched, the status, the response time, the key or app, the member it acted as, the client IP, the error code, the request ID and, for MCP requests, the MCP method and tool.
  • The route is the template the request matched, not the full URL: ids in the path and query values are not stored. Request and response bodies, headers and keys are never stored.

Not logged:

  • Attempts with an unknown or invalid key, or an app token that was refused. They have no verifiable owner in your organization.
  • Requests with a valid key for an organization its owner is not a member of.
  • What people do in the yggy app in a browser.

A request can be missing if yggy restarts at the moment it is handled. The log is for finding problems; the audit log is the record of who did what.

Rate-limited requests

Section titled “Rate-limited requests”

When a key goes over its hourly limit, yggy answers 429 with error.code RATE_LIMITED and a Retry-After header with the wait in seconds. These requests appear in the log with the rate limited tag and count towards the Rate limited total. See Errors and rate limits.

Who sees what

Section titled “Who sees what”
  • Members see their own requests: the ones made with their personal keys, with organization keys they created, and by apps they connected.
  • Owners and admins see every request in the organization, with the member each one acted as. The credential filter narrows the list to one key or app.
  • The log is only in the yggy app. API keys cannot read it.

Retention

Section titled “Retention”

Requests are kept for 30 days. They are not part of the self-service data export; access requests for them are handled with other personal data. On Pro and Enterprise, admins can also stream requests to their own log tool: see Export logs over OTLP.

Request IDs

Section titled “Request IDs”

Every API response carries an x-request-id header. It is the Request ID in the log. Log it in your client, and quote it when you contact support, so the request can be found again.

If you send your own x-request-id header of up to 200 characters, yggy uses that value and returns it, so you can match a request to your own logs.