Daily, weekly or monthly performance report for a past date: total requests, error rate, p95, top 20 transactions by impact and a timeline. Use to compare days or weeks. A period that has not ended covers only its finished hours (pendingBuckets > 0), and today has no data until it ends; compare such periods per day or use tideways_get_performance_summary. Covers production and the project's default service only; for another environment or service use tideways_get_performance with end and minutes=1440 (one day per call).

Get one issue from tideways_list_issues in depth: the stack trace of its latest occurrence (first 15 frames) with the request it came from (URL, method, status, host, service), the transactions it occurred in with counts, and its occurrences per time bucket over the retention period. Use to point at the failing code, rank the affected endpoints, and say when the issue started, peaked or stopped. Pass the id and the type the issue was listed under.

Automatic findings Tideways made for a project: PHP configuration problems (e.g. OPcache buffers, timeouts) and code bottlenecks detected in traces (e.g. N+1 queries, sleep, waits). Use for a quick health check or optimization ideas. Findings do not name the affected requests, and the API cannot filter traces by bottleneck: give the user the link, whose page in the Tideways UI lists recent affected traces. Do not infer N+1 queries from slow-SQL issues.

Performance of any window of 1-1440 minutes ending at "end" (default now) within the last ~30 days: totals (requests, error rate, p95/median/average response time, time per layer), the top 20 transactions by impact, and a timeline. Older windows return zeros; use tideways_get_history for them. For 15-minute trends over 30 days use tideways_get_performance_summary.

Requests, errors and p95 response time in 15-minute buckets for the last hours hours (up to ~30 days), with totals. Use for trends, before/after comparisons and spotting incidents. For per-minute detail and top transactions use tideways_get_performance.

Timeline of one transaction over 1-1440 minutes ending at "end" (default now): per minute (or per bucket above 60 minutes) requests, errors, requests over the response-time target, p95/median/average and time per layer, plus totals with a response-time histogram. Use it to see when a transaction got slow and in which layer. Take transactionId from transactions[].id of tideways_get_performance.

List error, slow-SQL, deprecation, warning or notice issues of a project, newest occurrence first, 10 per page, with the total count. Use to find what is failing or slow and how often. Reads all services unless "service" is passed or configured; "transactionIds" narrows to issues of given transactions. One type and one status per call. There is no time filter; use lastOccurred to judge recency.

List the projects and scopes of the configured Tideways API token, and how much of the organization's hourly rate limit is left. Call this first when unsure which project to use, or after a scope or unknown-project error.

List the services of a project (web, APIs, workers, CLI) named by its issues, the default service first. Call it when the user names an app, API or worker that is not a project, or a transaction that tideways_search_traces does not find in the default service, with "search" set to one word of it: each service is searched for that word and the services are sorted by matching traces, so the first ones serve it. Costs 4 requests, plus 1 per service searched: at most 30, fewer when the hourly rate limit is small or nearly used up. Only services named by the newest open or ignored issues are listed; the Tideways UI service selector lists all.

Find individual request traces (30 per call unless "limit" asks for up to 100; newest first unless sortBy is set) with response time, memory, bottlenecks and the slowest layers. Use to investigate specific slow or failing requests; filter by transaction IDs from tideways_get_performance, text, time window and response time.