ZeroBounce Logo

Docs

Language Icon
  • Sign In
  • Sign Up Free

Languages

ZeroBounce ImageGetting Started
ZeroBounce ImageEmail List Validation
ZeroBounce ImageA.I. Email Scoring
ZeroBounce ImageEmail Finder
ZeroBounce ImageDomain Search
ZeroBounce ImageActivity Data
ZeroBounce ImageMulti-file upload
ZeroBounce ImageIntegrations
ZeroBounce ImageUsage Reports
ZeroBounce ImageYour ZeroBounce Account
ZeroBounce ImageEmail Validation API
ZeroBounce ImageEmail Finder API
ZeroBounce ImageDomain Search API
ZeroBounce ImageA.I. Scoring API
ZeroBounce ImageActivity Data API
ZeroBounce ImageList Evaluator API
ZeroBounce ImageApi Dashboard
ZeroBounce ImageAPI Wrappers
ZeroBounce ImageAPI Migration
ZeroBounce ImageFAQ
ZeroBounce ImageAccount
ZeroBounce ImageUnderstanding email verification
ZeroBounce ImageUnderstanding email finder
ZeroBounce ImageUploading Files
ZeroBounce ImageBilling and Payments
ZeroBounce ImageQuestions about our services
ZeroBounce ImageData security and privacy
ZeroBounce ImagePotential Issues
ZeroBounce ImageIntegration and compatibility
ZeroBounce ImageEmail finder and enhancement
ZeroBounce ImageTroubleshooting and support
ZeroBounce ImageUpdates and innovations
ZeroBounce ImageTutorials and guides
ZeroBounce ImageAPI FAQs
ZeroBounce ImageWhy Am I Receiving a 403 Forbidden Error?
ZeroBounce ImageHow Do I Thread the API or Call the API Asynchronously?
ZeroBounce ImageWhy Does ZeroBounce Only Support TLS 1.2 and Above?
ZeroBounce ImageEmail Warmup FAQ
ZeroBounce ImageSecuring Your Account
ZeroBounce ImageAbout ZeroBounce
ZeroBounce ImageDeliverability Tools
ZeroBounce ImageStatus Page
  • Email Validation Homepage
  • Separator
  • Docs
  • Separator
  • Frequently Asked Questions
  • Separator
  • Api FAQs
  • Separator
  • How Do I Thread the API or Call the API Asynchronously?
Api FAQs

How Do I Thread the API or Call the API Asynchronously?

When using .NET, C#, or Visual Basic with the ZeroBounce email service API, you are limited to 2 outgoing Hypertext Transfer Protocol (HTTP) requests. In order to increase this to allow for threading or asynchronous API calls, you'll need to adjust the 'ServicePointManager.DefaultConnectionLimit' property. This property sets the maximum number of concurrent requests allowed by a ServicePoint object.

You can find documentation regarding this property via Microsoft's .NET and API browser documentation.

What is API threading?

Threading is a way for a program to split itself into two or more running tasks simultaneously (or pseudo-simultaneously). Multiple threads can be executed in parallel on many computer systems.

API threading can assist in improving the processing speed and performance of the ZeroBounce API from your device.

What does asynchronous mean in terms of the API?

Asynchronous means that multiple things will happen or process simultaneously. If you start a new action while running a program, the new action will take place without interrupting the other program.

Why would I need to thread the API or call asynchronously?

In a majority of cases, calling any API is considered an outgoing HTTP request. The potential issue with this is that most programming languages, as well as operating systems, have default limits in place that restrict the number of outgoing HTTP requests you may attempt. With these restrictions, you may face a slowdown when attempting to make multiple requests in a short period.

By threading the API, you can increase the limits so that you process a higher number of API requests asynchronously.

How do I get help with threading the ZeroBounce API?

If you're struggling with API threading using the documentation provided, please contact ZeroBounce support at support or via live chat.

The team can assist with all aspects of the email service API, including examining your API configuration and HTTP request limits. ZeroBounce's goal is for you to enjoy a seamless API experience with satisfactory results.

Related Articles

Why Am I Receiving a 403 Forbidden Error?

Why does ZeroBounce only support TLS 1.2 and above?