Parallel Webhook Delivery

We’ve launched parallel webhook delivery in our v19 release. This feature enables faster event processing, especially during high-load periods, but requires your webhook endpoints to handle concurrent requests.

Action Required: Ensure your endpoints can handle at least 20 concurrent requests before the migrating.

Steps to migrate

1. Test that you can receive events in parallel with our test tool.

2. Migrate topic by topic

3. Done

1. Test your parallel reception with our dedicated topic

• Create a new webhook using POST /webhookswith “topics”: [“migration_test_topic“]

• Call POST /webhook_topics/migration_test_topic/populate with {“messages”: X} to start production on the migration_test_topic topic. From there, you should receive parallelized requests in your webhook.

  • Maximum X is: 10000

  • Responses body is:

    { "test_id": string "message_number": int "timestamp": int }

  • In order to prevent spam, a test started by calling this route will be considered active for 1 to 300 seconds depending on the X chosen. A new test cannot be started while a previous test is ongoing.

• If everything looks fine, migration route POST /webhook_topics/{topic}/migrate_multipartition can be called for each topic you wanna migrate to parallelized mode

2. Migrating Your Topics

Migrate each topic individually using the following API endpoint:

Prerequisites for successful migration:

• All webhooks for the topic must be active.

Once migrated, webhook events for that topic will be delivered in parallel.

Learn more how order is handled here