Add support for 'verify_batch_events_request=>false'

[danielbachhuber]

See https://posthog.slack.com/archives/C03P7NL6RMW/p1741208127179239
See https://posthog.slack.com/archives/C07L8G1HVQR/p1741196816062289

Changes

Adds support for a 'verify_batch_events_request' => false setting when initializing PostHog. This will allow batch events requests to be sent in a non-blocking manner when using the LibCurl default transport.

Testing

To test, add some delay to the deprecated capture endpoint on your local PostHog install:

diff --git a/posthog/api/capture.py b/posthog/api/capture.py
index 8a1397c113..c6fe4cdf06 100644
--- a/posthog/api/capture.py
+++ b/posthog/api/capture.py
@@ -405,6 +405,8 @@ def lib_version_from_query_params(request) -> str:
 def get_event(request):
     structlog.contextvars.unbind_contextvars("team_id")
 
+    time.sleep(20)
+
     # handle cors request
     if request.method == "OPTIONS":
         return cors_response(request, JsonResponse({"status": 1}))

Then, download this test script to somewhere you can run PHP and apply an API key:

<?php

require_once __DIR__ . '/vendor/autoload.php';

use PostHog\PostHog;

const POSTHOG_API_KEY = "your_api_key";

PostHog::init(
    POSTHOG_API_KEY,
    array('host' => 'http://localhost:8000', 'ssl' => false, 'verify_batch_events_request' => false),
);

$distinctId = uniqid();

PostHog::capture(array(
    'distinctId' => $distinctId,
    'event' => 'php-test user signed up - ' . $distinctId
));
error_log('captured ' . $distinctId);

With 'verify_batch_events_request' => false, the test script should execute right away and your event should appear in your activity log.

With 'verify_batch_events_request' => true, the test script should take ~20s to execute and your event should appear in your activity log.