TripWorks records every REST API request and every AI assistant call, and shows them in a set of screens you can read, filter, and search. You can see how many requests your integrations made, which ones failed and why, which key made each one, and exactly what was sent and returned. This article walks through each screen and shows how to use them to find and fix a problem.

Where do you find API activity?

Go to Setup Integrations and open the REST API card. The tabs across the top are Overview, Keys, Limits, Logs, and API reference. Use Overview for the big picture and Logs for individual requests. AI assistant activity is on the AI Assistants card, covered at the end of this article.

What does the Overview show?

The Overview summarizes activity across all of your keys. Each chart has its own time range, which you change with the dropdown in its corner.

1. Monthly totals. Requests this month across all keys, the data transferred, and your error rate, with the number of failed requests behind it.
2. Requests. A chart of successful and failed requests over time, so you can see when traffic changed and whether failures spiked with it.
3. Errors by code. How many failed requests had each error code, so the most common problem stands out.
4. Errors list. The same failures grouped by error code and operation, with how many times each happened and when it last did. Use Previous and Next to move through the list.

How do you search the Logs?

Select the Logs tab to see individual requests, newest first, in pages. Each row shows the time, the status, the endpoint, the key that made the request, how long it took, and the size of the response.

1. Filters. Narrow the list by time, Outcome, Endpoint, Credential, or Error code. Combine them to answer a question such as which failures one key had on one endpoint last week.
2. Find by request ID. Paste a request ID to jump straight to that request.
3. Status. Each row shows the result, such as 200 for success or 429 Rate limited, so failures are easy to spot.
4. Credential. The name of the key that made the request, with its last four characters. Name your keys after the integration so this column tells you what was running.

What does a single request tell you?

Select any row to open the request. It shows what was sent, what came back, and how long it took, and every request has its own address, so you can bookmark it or paste it into a ticket. The arrows at the top step to the previous or next request, and Copy buttons let you copy any section.

1. Status. Whether the request succeeded, with its status code.
2. Request ID. The unique ID for this request. Select the copy icon to copy it, and quote it when you ask for help.
3. Credential. The key that made the request.
4. Correlation ID. A second ID labelled For TripWorks support. Include it when you contact support so they can trace the request on their side.

Below those, you can also see the time, duration, IP address, and the request and response size. Request headers are shown with secrets removed, so a key never appears in the log. Query parameters shows what you filtered on, and Response body shows exactly what TripWorks returned.

How do you find and fix a problem?

• A request failed. On Logs, set Outcome to failed, open a row, and read the status and the response body. The error code tells you what to change. See Handle errors and decisions in the REST API.
• You don't know which integration is responsible. Look at the Credential column, or filter by a key. If every integration has its own named key, this answers the question straight away.
• Requests are being rate limited. Filter Error code to too_many_requests, and check the Limits tab for the key that is running hot. See Build integrations that stay fast and efficient.
• A change looks wrong. Find the request that made it, open it, and compare the request with the response body to see what was sent and what TripWorks did with it.
• You need help from TripWorks. Open the request, copy the Request ID and the Correlation ID, and send both. Never send the key itself.
• A key may have been exposed. Filter Credential to that key and review everything it requested. Then rotate it. See How API keys and access work.

Where do you see what AI assistants have done?

When you connect Claude, ChatGPT, or Gemini, everything the assistant does is recorded too. Go to Setup Integrations, open the AI Assistants card, and select the Activity tab.

1. Views. Tool calls lists every call. Conversations groups calls into the conversations they belong to. What people try lets you review failed or denied calls.
2. Filters. Narrow by time, Outcome, Tool, AI client, or Error code, or search by request ID.
3. Outcome and tool. Whether the call worked, and which tool the assistant used, such as looking up customers or running a report.
4. AI client. Which assistant made the call.

Select a row to see the details of that call.

1. Approved by. The person who connected the assistant. The assistant acts as that person, so the call is limited by their permissions and credited to their name.
2. Correlation ID. The ID to give TripWorks support, as with an API request.
3. Arguments sent. The details the assistant passed to the tool.
4. Request body. The full request, so you can see exactly what was asked.

Changes an assistant makes also appear in your audit log under the name of the person who connected it, the same as a change they made in the web app.

Examples

• See what changed this week. Open Overview, set the Requests range to the last 7 days, and look for a spike in failed requests.
• Find the busiest error. In the Errors list on Overview, read the top entry to see which error code and operation fail most.
• Trace one failure. Paste a request ID into Find by request ID on Logs and read the response body.
• Check one integration. On Logs, filter Credential to your website's key and review its last requests.
• Ask support for help. Open the failed request and send the request ID and the correlation ID.
• Review an assistant. On the AI Assistants Activity tab, filter AI client to one assistant and open a call to see who approved it.

Frequently asked questions

Related

• Get started with the REST API
• How API keys and access work
• Handle errors and decisions in the REST API
• Build integrations that stay fast and efficient
• Connect TripWorks to your AI assistant (MCP)