How to view public API logs
Learn how to view, search, and troubleshoot API requests made using DoubleTick API keys and check request/response payloads, latency, and status codes.
Plan Availability: Pro & Enterprise
With Public API Logs, you can view and troubleshoot API requests made using your DoubleTick API keys directly from your account — track when an API was called, which key was used, whether it succeeded, and inspect the full request and response.
What's covered
What are public API logs?
The Logs tab gives you a real-time history of every API call made to DoubleTick using your organization's API keys. Earlier, verifying API activity or diagnosing a failed request meant reaching out to the support team — with Public API Logs, you get complete self-serve visibility to inspect and debug requests on your own.
Where can I find public API logs?
Log in to your DoubleTick account and open Settings.
Under the developer section, click Developer Documentation
At the top of the page, switch to the Logs tab.
You'll now see a list of every API call made to your account, with the most recent one at the top.
What you'll see in each log entry
Each row in the list gives you a quick summary of one API call:
Key name – the API key that made the request. If a request was made in a way that isn't tied to a named key, it will show as "Unknown key."
API URL – the specific endpoint that was called, such as a customer lookup or a chat assignment.
Timestamp – the exact date and time the call was made, in your account's local time.
Status – a green Success badge or a red Failed badge, so you can spot problems at a glance.
To find a specific call, use the search bar to look up a request by key name or URL. If you're trying to narrow things down further, use the two filters above the list:
All statuses – filter the list to show only successful calls or only failed ones.
All time – limit the results to a specific date range, useful when you're troubleshooting an issue from a particular day.
How to view request details
Click on any log entry and its full details will open on the right-hand side of the screen. This is where you get the complete picture of what was sent and what was returned:
API URL, HTTP status, and method – confirms exactly which endpoint was hit, whether it returned a code like 200 (success) or an error code, and whether it was a GET, POST, or another type of request.
Latency – how long DoubleTick took to respond, in milliseconds. If your integration feels slow, this tells you whether the delay is happening on our end.
Timestamp – the precise moment the request was received.
Request headers and request body – the exact data your application sent to DoubleTick, including the request payload (for example, a customer's phone number in a lookup request).
Response headers and response body – the exact data DoubleTick sent back, including any error messages if something went wrong.
For your security, sensitive details like your API key are automatically masked (shown as [REDACTED]) in the logs, so it's safe to review this information or share it with your team without exposing your credentials.
How to troubleshoot with logs
Use the Logs tab to find out why an integration failed.
Filter the list by Failed to find requests that did not work.
Open a failed request. Check the HTTP status and response body.
Read the error message. It may show invalid data, an expired key, or a missing field.
Compare the request body with the data your integration should send.
Check the timestamp for failures at the same time. This may point to a recent change in your system.
If you review the details and are still unsure why a call is failing, reach out to our support team with the request's timestamp and API URL handy — this lets us pull up the exact log and help you resolve it faster.
Log retention and limits
Capacity limit: each organization can store up to 50,000 API log entries.
Automated pruning: DoubleTick checks your logs every 5 minutes. If you have more than 50,000 logs, the oldest ones are automatically removed so that only the latest 50,000 logs are kept.
Key takeaways
Access logs via Settings → Developer API → Logs, right next to your API keys.
Filter entries by status, date range, API key name, or endpoint URL.
Inspect request/response payloads, headers, latency, and status codes to solve integration bugs fast.
Sensitive fields — tokens, passwords, phone numbers — are masked or encrypted automatically.
Your account keeps the latest 50,000 logs; older entries are pruned automatically every 5 minutes.
Frequently asked questions
Related articles
Last updated