> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/support-legal-and-others/troubleshooting-guide-for-getint-users/debug-requests-feature.md).

# Debug Requests Feature

When it comes to debugging, having access to the right information is crucial. On Getint, customers can share their connections with us, allowing us to retrieve specific fields and perform more detailed debugging. Here’s how to do it:

### How to Enable the Debug Option <a href="#how-to-enable-the-debug-option" id="how-to-enable-the-debug-option"></a>

Activating the **Debug** option for logs allows us to retrieve more detailed information in the synchronization logs and thoroughly examine potential issues. The **Info** option doesn't provide enough detail to troubleshoot the issue properly.

Go to **Settings** > **Data Storage**, then change the Log minimum level from **Info** to **Debug.**

<figure><img src="/files/o5RbXNtFolEOkpsB2iQE" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The debug option doesn't bring more information from previous logs. You'll need to rerun your integration to capture more details about the issues you’re experiencing.
{% endhint %}

### Debug Requests Feature <a href="#debug-requests-feature" id="debug-requests-feature"></a>

There are several ways to grant access to Getint if you need assistance from our team. [Here](https://docs.getint.io/getintio-platform/settings/sharing-access-permission), you'll find a detailed guide on how to share access permissions and allow our support team to address any issues you may experience.

Additionally, it's crucial to share the connection with us to ensure we have sufficient permissions to download the necessary information from your account. Follow these steps:

1. Go to **Connections** within Getint.
2. Locate the specific connection you're experiencing issues with.
3. Click the **three-dot button** on the right and select **Edit.**
4. Modify the access settings to **Anyone in Workspace can edit.**

<figure><img src="/files/Stzz8i2W6GpJDHyWWxHK" alt=""><figcaption></figcaption></figure>

Once you've approved access to Getint, we'll utilize the **Debug requests** option within Connections to download relevant REST API responses and effectively troubleshoot your issue.

<figure><img src="/files/MOJtMFpjXemz7fmBGgfB" alt=""><figcaption></figcaption></figure>

### Conclusion

Sharing access for detailed debugging on Getint is a straightforward process that can greatly enhance the troubleshooting process. By following these steps, customers can ensure that they are providing all the necessary information for detailed debugging, leading to faster and more efficient issue resolution.

<figure><img src="/files/otyodSR2k1YTwh3mrnVq" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team
">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.getint.io/support-legal-and-others/troubleshooting-guide-for-getint-users/debug-requests-feature.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
