> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/developers/webhooks/connection-settings.md).

# Connection Settings

The following connection settings are applied to every Webhook you configure.

<table data-full-width="true"><thead><tr><th>Connection Setting</th><th>Value</th><th>Description</th></tr></thead><tbody><tr><td>Connection Timeout</td><td>5,000</td><td>The timeout in milliseconds KORE will wait to establish its TCP connection to your web server.</td></tr><tr><td>Read Timeout</td><td>15,000</td><td>The amount of time in milliseconds after sending your Webhook an HTTP request that KORE will wait for the initial HTTP response packet. It also applies to how long KORE will wait between individual packets within your HTTP response.</td></tr><tr><td>Total Time</td><td>15,000</td><td>The total time allowed for all timeouts, including retries. If not set, the maximum limit is enforced.</td></tr><tr><td>Retry Count</td><td>1</td><td>The number of retry attempts KORE will make if its connection to your Webhook fails. To make sure you capture the behaviors you need, make sure to set the Retry Policy value below accordingly</td></tr><tr><td>Retry Policy</td><td>Connection timeouts or Server errors</td><td>A retry will be attempted if the HTTP return codes are 408 (Request Timeout) or 423 (Too many requests) or 5xx (Server Error)</td></tr></tbody></table>


---

# 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://docs.korewireless.com/kore/developers/webhooks/connection-settings.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.