NeverBounce provides email verification services to ensure the validity of email addresses, enhancing deliverability and reducing bounce rates.
Available to claim
Build and ship the NeverBounce plugin to earn 22 points when we merge it to main. You have 1 hour to link an issue, then 3 hours to open a PR with the plugin scaffold.
Tool to confirm proof of email ownership (POE) from the JavaScript widget. Use when verifying server-side that a user confirmed their email through the widget.
Tool to create a new bulk verification job with parsing, sampling, and callback options. Use for asynchronous list verification with advanced control.
Tool to permanently delete a job and its results. Use when you need to irreversibly remove a bulk verification job. This delete is irreversible.
Tool to download job results as a CSV file via GET. Use after job completion to retrieve segmented or enriched CSV output.
Tool to get account information including credits, job counts, and usage statistics. Use when retrieving NeverBounce account summary after authentication.
Tool to get the status and progress of a bulk verification job. Use when
Tool to send widget form events via the JS widget API. Use when reporting form.load or form.completion events after user interactions with your form.
Tool to verify a single email address and gather additional information. Use when you need real-time validation at the point of entry.
Tool to parse a job created with auto_parse disabled. Use when you need to manually parse a job. Cannot reparse once parsed.
Tool to retrieve paginated results for a completed job, including original data and verification outcomes. Use after confirming job completion; avoid aggressive polling as repeated calls before completion risk rate limit errors.
Tool to search and list bulk verification jobs in your account with pagination and filtering. Use when retrieving jobs by id, filename, or status, or when listing all jobs with pagination.
Tool to start a parsed job when auto_start is disabled. Use when you need to manually initiate a job that was created with auto_start=false.
No webhooks.
