Home/HighLevel/Features/App Marketplace/HighLevel marketplace webhook retries: how they work

Mobile and Desktop Apps

HighLevel marketplace webhook retries: how they work

In short

Automated Webhook Retries is a built in feature for HighLevel Marketplace apps that automatically resends webhook payloads when the receiving endpoint returns HTTP 429. It attempts up to six retries on a 10 minute interval with random jitter, and applies exponential backoff for other transient failures, improving delivery reliability.

AreaApp Marketplace · Get Started with App Marketplace
Used forSaaS startup, Marketing agency, Ecommerce platform
Setup steps4 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Marketplace app developers, because they need reliable event delivery during rate limit spikes.
  • Developers using Marketplace webhooks, because the retry schedule gives a longer recovery window for temporary endpoint issues.

02Automated webhook retries, explained

The feature watches the HTTP status returned by your webhook endpoint. If the response is 429 Too Many Requests, HighLevel will resend the same payload up to six times. Each attempt occurs roughly ten minutes after the previous one, with a small random jitter to avoid synchronized spikes.

For failures other than 429, the platform switches to an exponential backoff strategy that can continue for up to three days.

03How businesses use automated webhook retries

  • SaaS startup. The startup configures its webhook endpoint to always answer 200 OK after receiving a payload, even if internal processing is queued. When the service is momentarily overloaded, it returns 429 to trigger the built in retry flow, ensuring no user event is lost.
  • Marketing agency. The agency’s integration sends campaign data to an external analytics server. If the analytics API temporarily rate limits requests, the agency returns 429, letting HighLevel retry automatically instead of building a custom retry mechanism.
  • Ecommerce platform. The platform acknowledges order notifications with 200 OK. When its order processing microservice is down, it replies with 408 or 5xx as needed; HighLevel will stop retries for 5xx but will use exponential backoff for 408, giving the platform time to recover.

04The numbers and rules that matter

  • Interval: 10 minutes between retries (with jitter).
  • Max attempts: 6 retries.
  • Total retry duration: ~1 hour 10 minutes.
  • Non 429 retries can continue for up to 3 days.
  • Payload size limit: 256 KB.

05How to set up and use automated webhook retries in HighLevel

Configure webhook endpoint responses for retries

  1. Return a 200 OK status for every successful receipt of a webhook payload.
  2. If internal processing fails after acknowledgment, still respond with 200 OK to confirm receipt.
  3. Only use error codes when necessary: send 408 for timeout conditions, 429 when you need HighLevel to pause and retry, and 5xx for hard server failures that should stop further retries.
  4. No setup changes are required for developers already using externally shared Marketplace webhooks.

06What it looks like in HighLevel

07Things to know before you rely on it

  • Retries occur only when the endpoint returns a 429 response.
  • A maximum of six retry attempts are made for a 429 event.
  • Each retry is scheduled about ten minutes after the previous attempt, with a small random jitter.
  • The total possible retry window for 429 responses is roughly one hour ten minutes.
  • Non 429 failures follow an exponential backoff strategy and may be retried for up to three days.
  • Responses with 5xx status codes are treated as permanent failures; no further retries are performed.
  • The retry interval and number of attempts cannot be customized.
  • Webhook payloads are limited to 256 KB; larger payloads are truncated and flagged.

08How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

From my experience, the built in six attempt, jittered schedule provides a safety net that can help when occasional rate limit spikes occur. If your app rarely hits rate limits or you already have a robust internal queue handling, the added retries may not justify the extra load on your servers. In those cases you’ll spend time handling duplicate events and monitoring longer retry windows for little practical gain.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about automated webhook retries.

Will HighLevel deduplicate events across retries?

Yes. Each retry carries the same deliveryId header, allowing you to ignore duplicate deliveries.

Can I customize the retry interval or number of attempts?

No. The platform uses a fixed ten minute interval and a maximum of six attempts for 429 retries.

Which HTTP response codes should I return from my webhook endpoint?

Return 200 OK for successful receipt. Use 429 only when you need HighLevel to pause and retry. Return 408 for timeouts and 5xx for permanent server errors.

How long does the retry window last for a 429 response?

Retries are attempted roughly every ten minutes with jitter, up to six times, resulting in a total window of about one hour ten minutes.

Is there a size limit for webhook payloads?

Yes. Payloads cannot exceed 256 KB; larger payloads are truncated and marked with a payloadTooLarge flag.

Can I opt out of the automated retry logic?

No. The retry mechanism is built in and cannot be disabled per app; design your endpoint to handle possible duplicate deliveries.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.