LogoLogo
ProductsDevelopersAPI ReferenceContact Us
Developers
Developers
  • KORE Developer Experience Overview
  • API Management
    • API Clients
    • Authorization
    • API Responses
  • Webhooks
    • Connection Settings
    • Verifying Callbacks from KORE
    • Idempotency
  • Event Streams
    • Destinations
    • Streaming Rules
    • Events
  • Get Started
    • APIs
    • Webhooks
    • Event Streams
      • AWS Kinesis Quick Start
        • Script to Create a Kinesis Stream
      • Webhook Quick Start
  • How To ...
    • Invite and collaborate with developers
    • APIs
      • Refresh API Access Token
    • Webhooks
      • Validate Webhook Signatures
      • Rotate my Webhook Secret
      • Test and Troubleshoot my Webhook Integration
    • Event Streams
      • Test My Destination
      • Modify my Destination
      • Modify my Streaming Rule
On this page

Was this helpful?

  1. Webhooks

Connection Settings

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

Connection Setting
Value
Description

Connection Timeout

5,000

The timeout in milliseconds KORE will wait to establish its TCP connection to your web server.

Read Timeout

15,000

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.

Total Time

15,000

The total time allowed for all timeouts, including retries. If not set, the maximum limit is enforced.

Retry Count

1

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

Retry Policy

Connection timeouts or Server errors

A retry will be attempted if the HTTP return codes are 408 (Request Timeout) or 423 (Too many requests) or 5xx (Server Error)

PreviousWebhooksNextVerifying Callbacks from KORE

Last updated 9 months ago

Was this helpful?