Here are the most frequently asked questions about the API logs
Q: Where can I find API logs for a specific order?
A: You have two quick ways:
From the Dashboard: Go to Logs > API Logs for a master view of the whole chain.
From an Order: Search for the order in Order Search or Order Details. Look for the API Logs option in the action menu or the enhanced section that replaced "POS Errors." It’s a one-click jump to the data you need.
Q: How much historical data can I see?
A: By default, the system shows logs from the last 7 days to keep things fast. However, you can use the date picker to search back through anytime, start nad end date in history.
Q: Why don't POS logs type have separate tabs for "Request" and "Response" like the others?
A: Due to current technical limitations with POS integrations, we cannot split that data into separate tabs. Instead, we provide a Raw JSON tab. Don't worry—all the info (request, response, and errors) is contained within that single JSON record for your troubleshooting needs.
Q: How do I read the POS logs if they are just one big record?
A: Use the "Raw JSON" view. It contains the full payload of the transaction. You can still use the Copy or Download tools.
Q: Can I search for all errors at a specific restaurant?
A: Yes! Simply enter the Restaurant ID in the filter and set the Status Type to "Error." This is great for identifying if a specific store is having connectivity issues.
Q: How do I share a log with a partner or developer?
A: You have two "Pro" tools:
Copy to Clipboard: Click the copy button to grab the Metadata, Request, and Response. It will paste in a valid JSON format, so it’s ready for any developer tool.
Download Log: Click the download button to save the entry as a .txt or .json file to attach directly to a Jira ticket or email.
Q: Is there a way to copy just the error message?
A: Yes, you can copy specific sections (Summary, Request, or Response) individually, or the "Copy All" button to grab the whole journey at once.
Q: What information is included in the Metadata Summary?
A: Each log shows the Timestamp, Endpoint URL, Path, HTTP Method, Merchant ID, and the HTTP Status Code (like 200 for success or 500 for error).
Q: What happened to the "POS Error" section?
A: We’ve upgraded it! It has been replaced or enhanced by this new API Log view, which gives you much deeper context than the old error messages ever did