> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/developer-documentation/how-to-view-public-api-logs.md).

# 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?](#what-are-public-api-logs)
* [Where can I find public API logs?](#where-can-i-find-public-api-logs)
* [What you'll see in each log entry](#what-youll-see-in-each-log-entry)
* [How to view request details](#how-to-view-request-details)
* [How to troubleshoot with logs](#how-to-troubleshoot-with-logs)
* [Log retention and limits](#log-retention-and-limits)
* [Key takeaways](#key-takeaways)
* [Frequently asked questions](#frequently-asked-questions)

#### 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.

{% hint style="info" %}
Need instant updates from DoubleTick? Use webhooks. They automatically send event updates to your system. Learn more in [Understanding and using webhooks in DoubleTick](https://learn.doubletick.io/webhooks-and-public-api/webhooks/understanding-and-using-webhooks-in-doubletick).
{% endhint %}

#### Where can I find public API logs?

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FmXCO7vm4SyjQyzlGiHJC%2FUntitled%20design%20-%202026-08-27T150334.401.gif?alt=media&amp;token=19cc4eac-84b0-4b7f-98c7-fe5ee013f1c4" alt=""><figcaption></figcaption></figure>

* 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.

{% hint style="warning" %}
You need the **View API Keys** permission to access this tab. If you can't see it, ask your admin to grant it — see [how to set permissions for custom organization role](https://learn.doubletick.io/settings/manage-roles/how-to-set-permissions-for-custom-organization-role#api-management) for details.
{% endhint %}

#### What you'll see in each log entry

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2Fy2lBwGwy0xRjXj9j6Jbh%2Fimage.png?alt=media&amp;token=521661dd-909d-4dc1-a4f5-725a2121bf96" alt="" width="462"><figcaption></figcaption></figure>

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.

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2F45bka5PT0ZgLFaRDHV2W%2Fimage.png?alt=media&amp;token=00fdbb8e-d002-40f7-9a65-a11d0ec67982" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2F89LQixmdqc4nHBokJb8L%2FUntitled%20design%20-%202026-08-27T152042.769.gif?alt=media&amp;token=5cf9dff4-984b-4db8-9185-e948e3a38ef5" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FkmfKgBDLh6cTDqoATZ8F%2FUntitled%20design%20-%202026-08-27T153009.373.gif?alt=media&amp;token=02fc25dd-6199-4278-bad9-2e8366c87e2b" alt=""><figcaption></figcaption></figure>

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

<details>

<summary>Which plans include public API logs?</summary>

Public API Logs are available on Pro and Enterprise plans.

Starter accounts cannot view or search API activity.

</details>

<details>

<summary>Do I need a specific permission to view public API logs?</summary>

Yes, you need the View API Keys permission under API management.\
If this option isn't showing up in your Settings menu, ask an admin to grant it through Settings → Roles.

</details>

<details>

<summary>Can I view data from a failed API request?</summary>

Yes.\
Clicking a failed log entry shows the HTTP status code, the exact request body that was sent, and the error message returned in the response body — so you can see exactly what went wrong.

</details>

<details>

<summary>Are API keys or sensitive customer details visible in the logs?</summary>

No.\
Authorization headers, raw API keys, tokens, and passwords are stripped or masked, and phone numbers are encrypted before they're ever stored.

</details>

<details>

<summary>When are old API logs purged?</summary>

DoubleTick checks your log count every 5 minutes.\
If your account has more than 50,000 entries, the oldest logs are automatically deleted until you're back down to the latest 50,000.

</details>

#### Related articles

* [How to Create and Manage Your API Key in DoubleTick](/settings/developer-documentation/how-to-create-and-manage-your-api-key-in-doubletick.md)
* [How to Regenerate Your API Key in DoubleTick](/settings/developer-documentation/how-to-regenerate-your-api-key-in-doubletick.md)
* [How to set permissions for custom organization role](/settings/manage-roles/how-to-set-permissions-for-custom-organization-role.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/settings/developer-documentation/how-to-view-public-api-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.