{"openapi":"3.0.0","info":{"description":"EmailListVerify API for single and bulk email verification, credit balance and verification reports","version":"v1"},"servers":[{"description":"EmailListVerify API for single and bulk email verification, credit balance and verification reports","url":"https://api.apirails.com/emaillistverify"}],"paths":{"/api/verifyEmail":{"get":{"tags":["Email Validation"],"parameters":[{"name":"email","in":"query","description":"The email address that will be verified","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#verifySingleEmail","api_endpoint":"https://api.emaillistverify.com/api/verifyEmail"},"summary":"Verify email deliverability","description":"Verify email deliverability | ## Verify email deliverability\n#### Rate limit: 10 requests in 1 second\n#### Credits required: 1\nThis endpoint evaluates deliverability status of a single email address. The response body is a plain text representing the deliverability status. Additionally, the value can be `error_credit` which denotes inadequate credit balance for request execution. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}},"/api/verifyEmailDetailed":{"get":{"tags":["Verification"],"parameters":[{"name":"email","in":"query","description":"The email address that will be verified","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#verifySingleEmailDetailed","api_endpoint":"https://api.emaillistverify.com/api/verifyEmailDetailed"},"summary":"Verify email deliverability (verifyEmailDetailed)","description":"Verify email deliverability | ## Verify email deliverability\n#### Rate limit: 10 requests in 1 second\n#### Credits required: 1\nThis endpoint determines the deliverability status of an individual email address, providing information on evaluated metadata as part of the evaluation process. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}},"/api/emailJobs":{"post":{"tags":["Verification"],"parameters":[],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#createEmailJob","api_endpoint":"https://api.emaillistverify.com/api/emailJobs"},"summary":"Create asynchronous job that verifies email deliverability","description":"Create asynchronous job that verifies email deliverability | ## Create asynchronous job that verifies email deliverability\n#### Rate limit: 100 requests in 1 second\n#### Credits required: Based on the quality\n- **Standard:** 1 credit\n- **High:** 2 credits\nThis API endpoint initiates an asynchronous task to assess the deliverability status of an individual email address. Additionally, the result includes details on the processed metadata during the evaluation. Users need to query the job later to check its progress or access the final outcome. Please be aware that jobs of **standard** quality may require up to 1 minute for completion, whereas **high** quality jobs may take up to 30 minutes due to potential greylisting delays. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{"email":{"type":"string","description":"The email address that will be verified asynchronously","required":true},"quality":{"type":"string","description":"Quality of the email verification. If not present, the default value is **standard**"}}},"example":{"email":["john.smith@gmail.com"],"quality":["high"]}}}}}},"/api/emailJobs/{id}":{"get":{"tags":["Verification"],"parameters":[{"name":"id","in":"path","description":"id (path parameter from the official API reference)","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#getEmailJob","api_endpoint":"https://api.emaillistverify.com/api/emailJobs/{id}"},"summary":"Verify email deliverability (id)","description":"Verify email deliverability | ## Verify email deliverability\n#### Rate limit: 100 requests in 1 second\nThis endpoint retrieves status of an asynchronous email job including result and information on evaluated metadata if it's already finished. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}},"/api/verifyApiFile":{"post":{"tags":["Verification"],"parameters":[],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#verifyApiFile","api_endpoint":"https://api.emaillistverify.com/api/verifyApiFile"},"summary":"Upload email list","description":"Upload email list | ## Upload email list\n#### Rate limit: 5 requests in 1 second\n#### Credits required: Based on the number of valid and unique emails found in the file and the quality\n- **Standard:** 1 credit per email\n- **High:** 2 credits per email\nBefore you begin the upload, make sure your email list file meets these formatting requirements:\n  - The file format is *.csv*, *.txt*, or *.xlsx*\n  - One email address per row\n  - File does not exceed 100 MB\n  - Email addresses are placed in the same column\n  - The spreadsheet should not have more than 1,000,000 rows\nFor example, this is a valid email list:\n| First Name | Last Name | Email | Company | Phone | Added |\n| ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |\n| Sienna | Schuster | Sienna_Schuster91@gmail.com | Haley and Bechtelar | (719) 472-6351 x8875 | Apr 3rd 2025 |\n| Kale | Parker | Kale.Parker9@yahoo.com | Kub LLC | 790.549.8766 x9145 | Feb 6th 2024 |\n| Florine | Sipes | Florine.Sipes@hotmail.com | Marquardt LLC | (881) 624-2788 x120 | Mar 6th 2025 |\n| Rebeca | Grady | Rebeca.Grady@hotmail.com | Buckridge - Kshlerin | (245) 226-4323 | May 1st 2025 |\n| Jeanie | McGlynn-Dicki | Jeanie_McGlynn-Dicki@yahoo.com | O'Connell Group | 1-773-534-2564 | Dec 12th 2024 |\n| Adela | Franey | Adela_Franey17@gmail.com | Connelly Inc | 1-638-484-8311 x2970 | Dec 14th 2023 |\n| Carmela | Sipes | Carmela_Sipes@hotmail.com | Lubowitz and Schowalter | 507-649-5761 x31543 | Mar 30th 2024 |\n| Ladarius | Metz | Ladarius.Metz@yahoo.com | Glover - Ziemann | (871) 854-6314 x525 | Oct 29th 2025 |\n| Allen | Hirthe | Allen.Hirthe49@hotmail.com | Schuppe - Lemke | 1-462-480-1998 x9315 | May 22nd 2024 |\nAnd its corresponding raw *.csv* file ready for upload:\n```\nFirst Name,Last Name,Email,Company,Phone,Added\nSienna,Schuster,Sienna_Schuster91@gmail.com,Haley and Bechtelar,(719) 472-6351 x8875,Apr 3rd 2025\nKale,Parker,Kale.Parker9@yahoo.com,Kub LLC,790.549.8766 x9145,Feb 6th 2024\nFlorine,Sipes,Florine.Sipes@hotmail.com,Marquardt LLC,(881) 624-2788 x120,Mar 6th 2025\nRebeca,Grady,Rebeca.Grady@hotmail.com,Buckridge - Kshlerin,(245) 226-4323,May 1st 2025\nJeanie,McGlynn-Dicki,Jeanie_McGlynn-Dicki@yahoo.com,O'Connell Group,1-773-534-2564,Dec 12th 2024\nAdela,Franey,Adela_Franey17@gmail.com,Connelly Inc,1-638-484-8311 x2970,Dec 14th 2023\nCarmela,Sipes,Carmela_Sipes@hotmail.com,Lubowitz and Schowalter,507-649-5761 x31543,Mar 30th 2024\nLadarius,Metz,Ladarius.Metz@yahoo.com,Glover - Ziemann,(871) 854-6314 x525,Oct 29th 2025\nAllen,Hirthe,Allen.Hirthe49@hotmail.com,Schuppe - Lemke,1-462-480-1998 x9315,May 22nd 2024\n```\nAfter successfully uploading the email list, the HTTP response will return an ID which you can use to query for the bulk verification progress using the endpoint `/api/maillists/{id}/progress`. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":false,"content":{"multipart/form-data":{"schema":{"type":"object","required":[],"properties":{"deepScan":{"type":"string","description":"When set to **true**, a Deep Scan is automatically started once the first verification pass finishes. Deep Scan re-verifies unresolved emails (results like _unknown_ or _antispam_system_) with high verification quality, at a cost of **3 credits per re-verified email**. Only the values `true` and `false` are accepted — anything else is rejected with a validation error. See the `/api/maillists/{id}/reverify` endpoint for details."},"file_contents":{"type":"string","description":"body.file_contents (string field from the documented request schema)","required":true},"quality":{"type":"string","description":"Quality of the email list verification. If not present, the default value is **standard**"}}},"example":{"deepScan":["false"],"file_contents":["string"],"quality":["high"]}}}}}},"/api/findContact":{"post":{"tags":["Verification"],"parameters":[],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#findContact","api_endpoint":"https://api.emaillistverify.com/api/findContact"},"summary":"Search for email address of a contact","description":"Search for email address of a contact | ## Search for email address of a contact\n#### Rate limit: 5 requests in 1 second\n#### Credits required:\n- **5:** If the first name, the last name, or both are provided.\n- **10:** If only the domain is provided.\nThis endpoint is specifically configured to facilitate the discovery of a contact's **business email address**. By supplying the contact's optional first name, optional last name, and mandatory company email domain, a series of potential email addresses will be generated. These addresses will then undergo verification for deliverability, following which our **level of confidence** in each email will be assessed to identify the most appropriate match for the contact's primary email address.\nThe variety and quantity of emails generated will be dependent on the presence of optional parameters:\n- **Both First Name and Last Name:** A search will be conducted for several potential combinations of the name format (e.g., *john.smith@company.com*, *smithjohn@company.com*).\n- **Only One of the Names:** A search will be carried out for one potential email address (e.g., *john@company.com*).\n- **Only Domain:** A search will be conducted for around twenty business-related emails associated with the company (e.g., *info@company.com*, *support@domain.com*).\nGiven that the number of emails generated for verification may vary, distinct credit amounts are charged accordingly.\nLastly, the confidence levels assigned to each generated email will fall into one of the following categories:\n- **high:** The email is deliverable and precisely aligns with the contact's name or the role within the company. It is expected to reach the intended recipient securely.\n- **medium:** The email is deliverable, although the contact's name may only be partially matched. The email might lead to a different person with a similar name within the company.\n- **low:** The email is deliverable, but the domain is associated with a free email service provider (e.g., _gmail.com_). This email may not reach the expected individual.\n- **unknown:** The email's deliverability is uncertain, or our verification was partially obstructed by anti-spam protection mechanisms. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{"domain":{"type":"string","description":"Email domain of the contact's company","required":true},"firstName":{"type":"string","description":"First name of the contact"},"lastName":{"type":"string","description":"Last name of the contact"}}},"example":{"domain":["connelycorp.com"],"firstName":["Adela"],"lastName":["Franey"]}}}}}},"/api/checkDisposable":{"post":{"tags":["Verification"],"parameters":[{"name":"domain","in":"query","description":"The email domain to check","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#checkDisposable","api_endpoint":"https://api.emaillistverify.com/api/checkDisposable"},"summary":"Verify if a domain is disposable","description":"Verify if a domain is disposable | ## Verify if a domain is disposable\n#### Rate limit: 50 requests in 1 second\n#### Credits required: 1\nThis API endpoint serves to determine if an email domain is associated with the generation of temporary email addresses. The purpose of this verification is to provide a faster alternative to the `verifyEmail` deliverability check, specifically for safeguarding registration endpoints. In addition to the disposability check, this operation includes the verification of the domain's DNS records for correct configuration. The response generated by this endpoint is formatted as a JSON object, with the `result` field indicating the disposability status of the domain. The `result` value can be one of the following:\n| Result | Description |\n| -------- | ------- |\n| `disposable` | The email domain is recognized for issuing temporary email addresses, which may result in bounced emails, non-receipt, or delivery to unintended recipients. |\n| `ok` | The email domain hosts legitimate email addresses and is capable of receiving incoming emails without issue. |\n| `dead_server` | Denotes that the email domain is nonexistent or lacks the appropriate MX server configuration, resulting in bounced emails back to the sender. |\n| `invalid_mx` | Indicates misconfigured MX servers for the email domain, leading to bounced emails returned to the sender. |\n| `unknown` | The presence of an unknown error prevents verification of the disposability status of the email domain, with no deduction of credits for the verification request. | | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{}},"example":{}}}}}},"/api/checkBlacklists":{"post":{"tags":["Verification"],"parameters":[],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#checkBlacklists","api_endpoint":"https://api.emaillistverify.com/api/checkBlacklists"},"summary":"Check IP or domain against blacklists","description":"Check IP or domain against blacklists | ## Check IP or domain against blacklists\n#### Rate limit: 10 requests in 1 second\n#### Credits required: 10\nThis API endpoint checks an IP address (IPv4 or IPv6) or domain against multiple DNS-based blacklists (DNSBLs) to determine if it has been listed for spam, malicious activity, or other reputation issues. The endpoint automatically detects the type of value provided (IPv4, IPv6, or domain) and queries the appropriate blacklist providers.\nThis check is useful for monitoring IP reputation, preventing spam, and ensuring email deliverability. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{"value":{"type":"string","description":"The IP address (IPv4/IPv6) or domain to check against blacklists","required":true}}},"example":{"value":["172.75.233.15"]}}}}}},"/api/maillists/{id}/progress":{"get":{"tags":["Verification"],"parameters":[{"name":"id","in":"path","description":"id (path parameter from the official API reference)","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#maillistProgress","api_endpoint":"https://api.emaillistverify.com/api/maillists/{id}/progress"},"summary":"Retrieve progress information of email list","description":"Retrieve progress information of email list | ## Retrieve progress information of email list\n#### Rate limit: 100 requests in 1 second\nRetrieve real-time progress updates for an uploaded email list. This endpoint offers insights into the verification process, with the `status` enum conveying the following values:\n| Status | Description |\n| ------ | ----------- |\n| `uploaded` | The email list has been successfully uploaded and is awaiting processing. |\n| `processing` | Verification of the email list is currently underway. Utilize the 'progress' property to monitor its completion. |\n| `finished` | Verification of the email list is complete. Access the download URL to obtain the results. |\n| `inQueue` | The maximum limit for concurrent email list verifications has been reached, set to 5 by default. The list will commence processing automatically as existing verifications are finalized. |\n| `starting` | The verification process for the email list is commencing. Emails are being queued for verification. |\n| `error` | Verification of the email list encountered an unknown error. **All credits have been returned** for this email list. |\nWhen a Deep Scan pass runs on the email list (see the `/api/maillists/{id}/reverify` endpoint), the `status` leaves `finished` (via `starting` or `inQueue`, then `processing`) and `progress` starts again from 0. Use the `deepScan` object to distinguish the verification phases.\nAdditionally, details regarding credit handling for the email list are provided, comprising two distinct values:\n - **charged:** The number of credits deducted based on the quantity of valid email addresses identified in the file. **Duplicate email addresses are not charged.**\n - **returned:** The number of credits returned when the email list is finished, for emails with non-chargeable verification results (e.g. _antispam_system_). | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}},"/api/maillists/{id}/reverify":{"post":{"tags":["Verification"],"parameters":[{"name":"id","in":"path","description":"ID of the finished email list","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#reverifyMaillist","api_endpoint":"https://api.emaillistverify.com/api/maillists/{id}/reverify"},"summary":"Start Deep Scan of finished email list","description":"Start Deep Scan of finished email list | ## Start Deep Scan of finished email list\n#### Rate limit: 1 requests in 1 second\nDeep Scan re-verifies emails from a finished email list that could not be resolved during the first pass\n(results like _unknown_ or _antispam_system_). The re-verification runs with high verification quality\n(multiple attempts and greylist handling), which typically recovers a significant portion of unresolved emails.\nKey details:\n - The email list must be in the `finished` status.\n - Deep Scan can be run **only once** per email list.\n - The cost is **3 credits per re-verified email**. Only unresolved emails are re-verified and charged.\n - The ID of the email list **does not change** — keep polling the same `/api/maillists/{id}/progress` endpoint.\n   The `status` changes to `starting` (or `inQueue` when the concurrent list limit is reached), then\n   `processing`, and `progress` starts again from 0 for the Deep Scan pass.\n - A backup copy of the original results is stored in your account as a new list prefixed with `reverify_`.\nAlternatively, you can schedule Deep Scan automatically when uploading a file by setting the `deepScan`\nparameter of the upload endpoint — the Deep Scan pass then starts as soon as the first pass finishes. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{}},"example":{}}}}}},"/api/maillists/{id}":{"get":{"tags":["Verification"],"parameters":[{"name":"id","in":"path","description":"ID of the finished email list","required":true,"schema":{"type":"string","example":""}},{"name":"addDuplicates","in":"query","description":"Eliminates duplicate emails from the email list, retaining only the first occurrence of each email.","required":false,"schema":{"type":"string","example":""}},{"name":"addEmail","in":"query","description":"Adds a column named 'ELV Email' displaying the exact email that was used as an input during the verification process.","required":false,"schema":{"type":"string","example":""}},{"name":"addEsp","in":"query","description":"Adds a column named 'ELV ESP' displaying the Email Service Provider associated with the domain of the email.","required":false,"schema":{"type":"string","example":""}},{"name":"addFirstName","in":"query","description":"Adds a column 'ELV First Name' with an estimation of the first name of the person associated with the email address.","required":false,"schema":{"type":"string","example":""}},{"name":"addGender","in":"query","description":"Adds a column named 'ELV Gender' with an estimation of the gender of the person associated with the email address.","required":false,"schema":{"type":"string","example":""}},{"name":"addInternalResult","in":"query","description":"Adds a column named 'ELV Internal Result' displaying the internal verification result given by the system.","required":false,"schema":{"type":"string","example":""}},{"name":"addIsFree","in":"query","description":"Adds a column named 'ELV Is Free' containing values that indicate the potential for creating a free email account using the same domain.","required":false,"schema":{"type":"string","example":""}},{"name":"addIsNoReply","in":"query","description":"Adds a column named 'ELV Is No Reply' with values denoting whether the email's inbox is actively monitored for incoming messages. Typically, these emails feature names such as 'noreply' or 'no-reply'.","required":false,"schema":{"type":"string","example":""}},{"name":"addIsRole","in":"query","description":"Adds a column named 'ELV Is Role' to signify if the email pertains to a specific business-related role within a company rather than an individual. Such emails typically feature names such as 'info' or 'support'.","required":false,"schema":{"type":"string","example":""}},{"name":"addLastName","in":"query","description":"Adds a column named 'ELV Last Name' with an estimation of the last name of the person associated with the email address.","required":false,"schema":{"type":"string","example":""}},{"name":"addMxServer","in":"query","description":"Adds a column named 'ELV MX Server' displaying the MX server associated with the domain of the email.","required":false,"schema":{"type":"string","example":""}},{"name":"addNoEmailRows","in":"query","description":"Adds rows that do not contain precisely one email and cannot undergo verification due to insufficient input. These rows are assigned a blank deliverability status (-)","required":false,"schema":{"type":"string","example":""}},{"name":"addOriginal","in":"query","description":"Includes all columns from the uploaded file that do not contain email information (e.g., Phone, Address).","required":false,"schema":{"type":"string","example":""}},{"name":"addResult","in":"query","description":"Adds a column named 'ELV Result' displaying the result of the verification process of the row's email.","required":false,"schema":{"type":"string","example":""}},{"name":"format","in":"query","description":"Select the format of the downloaded email list file.","required":false,"schema":{"type":"string","example":"","items":{"type":"string","enum":["csv","xlsx"]}}},{"name":"results","in":"query","description":"Adds rows containing the verification result within this parameter. The parameter's value comprises a list of deliverability statuses separated by commas.","required":false,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#downloadMaillist","api_endpoint":"https://api.emaillistverify.com/api/maillists/{id}"},"summary":"Download finished email list","description":"Download finished email list | ## Download finished email list\n#### Rate limit: 5 requests in 1 second\nOnce the verification of the email list is completed, you have the option to download the result file, which includes the verification outcomes in a distinct column. By default, a single column is added on the far left, identified by the custom header 'ELV Result'. This column showcases the verification status of each row's email address. If a row contains either no email addresses or more than two, making it challenging to select valid input for verification, the result field displays a blank value (-). Here is an example of the downloaded result without utilizing any query parameters:\n| ELV Result | First Name | Last Name | Email | Company | Phone | Added |\n| ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |\n| dead_server | Sienna | Schuster | Sienna_Schuster91@gmail.com | Haley and Bechtelar | (719) 472-6351 x8875 | Apr 3rd 2025 |\n| invalid_mx | Kale | Parker | Kale.Parker9@yahoo.com | Kub LLC | 790.549.8766 x9145 | Feb 6th 2024 |\n| invalid_mx | Florine | Sipes | Florine.Sipes@hotmail.com | Marquardt LLC | (881) 624-2788 x120 | Mar 6th 2025 |\n| spamtrap | Rebeca | Grady | Rebeca.Grady@hotmail.com | Buckridge - Kshlerin | (245) 226-4323 | May 1st 2025 |\n| smtp_protocol | Jeanie | McGlynn-Dicki | Jeanie_McGlynn-Dicki@yahoo.com | O'Connell Group | 1-773-534-2564 | Dec 12th 2024 |\n| dead_server | Adela | Franey | Adela_Franey17@gmail.com | Connelly Inc | 1-638-484-8311 x2970 | Dec 14th 2023 |\n| invalid_syntax | Carmela | Sipes | Carmela_Sipes@hotmail.com | Lubowitz and Schowalter | 507-649-5761 x31543 | Mar 30th 2024 |\n| dead_server | Ladarius | Metz | Ladarius.Metz@yahoo.com | Glover - Ziemann | (871) 854-6314 x525 | Oct 29th 2025 |\n| spamtrap | Allen | Hirthe | Allen.Hirthe49@hotmail.com | Schuppe - Lemke | 1-462-480-1998 x9315 | May 22nd 2024 |\nNevertheless, this endpoint provides a range of query parameters to customize the columns and rows of the email list file extensively. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]},"delete":{"tags":["Verification"],"parameters":[{"name":"id","in":"path","description":"ID of the finished email list","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#deleteMaillist","api_endpoint":"https://api.emaillistverify.com/api/maillists/{id}"},"summary":"Delete finished email list","description":"Delete finished email list | ## Delete finished email list\n#### Rate limit: 100 requests in 1 second\nOnce the verification of the email list is completed, you have the option to delete it. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{}},"example":{}}}}}},"/api/credits":{"get":{"tags":["Verification"],"parameters":[],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#credits","api_endpoint":"https://api.emaillistverify.com/api/credits"},"summary":"Retrieve details regarding your available credits","description":"Retrieve details regarding your available credits | ## Retrieve details regarding your available credits\n#### Rate limit: 10 requests in 1 second\nDescription of the available on-demand and daily credit allocations. On-demand credits retain their validity indefinitely, allowing flexibility in their utilization at any time. Daily credits are replenished on a daily basis and are accessible solely during the active subscription period. No credits are charged for this request. | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}},"/api/inboxPlacementTests":{"post":{"tags":["Inbox Placement Tests"],"parameters":[],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#createPlacementTest","api_endpoint":"https://api.emaillistverify.com/api/inboxPlacementTests"},"summary":"Create inbox placement test","description":"Create inbox placement test | ## Create inbox placement test\n#### Rate limit: 20 requests in 1 second\n#### Credits required: 10\nThis endpoint creates a new inbox placement test to evaluate where your emails land across different email service providers (Gmail, Yahoo, Outlook, etc.).\n### How it works:\n1. **Call this endpoint** to create a test. Optionally provide:\n   - A name for the test (for easier identification)\n   - A webhook URL to receive results automatically when the test completes\n2. **You will receive**:\n   - A unique tracking code (e.g., `ELV-A1B2C3D4E5`)\n   - A list of seed email addresses to send your test email to\n   - A test ID for polling results\n3. **Send a test email** from your production email system (the one you want to test) to **all** the provided seed email addresses\n4. **Include the tracking code** in your email subject or body so the system can identify your test\n5. **Get results** either by:\n   - Polling the `GET /api/inboxPlacementTests/{code}` endpoint every 30-60 seconds\n   - Waiting for automatic webhook notification (if webhook URL was provided)\n### Important notes:\n- The test typically completes within **5-10 minutes** after you send the emails\n- 10 credits are charged upfront\n- If no placement is detected (all emails missing/waiting), **the charged credits are refunded automatically**\n- If at least one email is detected (inbox/spam/promotions), the test is considered billable and credits are kept\n- Webhook notifications are sent as POST requests with the complete test results when status becomes \"complete\"\n### Example workflow:\n1. POST /api/inboxPlacementTests with optional name and webhookUrl parameters\n2. Receive tracking code and list of seed email addresses\n3. Send email from YOUR production system to all seed emails with tracking code in subject/body\n4. Get results via polling or webhook notification | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}],"requestBody":{"description":"","required":true,"content":{"application/json":{"schema":{"type":"object","required":[],"properties":{"name":{"type":"string","description":"Optional name for the placement test. If not provided, a default name will be generated."},"webhookUrl":{"type":"string","description":"Optional webhook URL for asynchronous result delivery. Must be a valid HTTP or HTTPS URL. When provided, a POST request with test results will be sent to this URL upon test completion."}}},"example":{"name":["Q1 2025 Campaign Test"],"webhookUrl":["https://yourapp.com/webhooks/placement-test"]}}}}}},"/api/inboxPlacementTests/{code}":{"get":{"tags":["Inbox Placement Tests"],"parameters":[{"name":"code","in":"path","description":"Tracking code of the placement test","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#getPlacementTest","api_endpoint":"https://api.emaillistverify.com/api/inboxPlacementTests/{code}"},"summary":"Get placement test results","description":"Get placement test results | ## Get placement test results\n#### Rate limit: 20 requests in 1 second\nThis endpoint retrieves the current status and results of a placement test.\n### Response includes:\n- **Status**: `running` or `complete`\n- **Recipients**: List of all seed emails with their current placement status:\n  - `inbox` - Email landed in primary inbox\n  - `category` - Email landed in promotions/social/updates folder\n  - `spam` - Email landed in spam folder\n  - `waiting` - Email not yet detected (test still running)\n  - `missing` - Email not found (may have bounced or blocked)\n- **Sender**: The email address that sent the test (detected automatically)\n- **ESP breakdown**: Results grouped by email service provider (Google, Yahoo, Outlook, etc.)\n### Polling recommendations:\n- Poll every **30-60 seconds** while status is `running`\n- Stop polling when status becomes `complete`\n- Tests typically complete within 5-10 minutes | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}},"/api/getApiFileInfo":{"get":{"tags":["Compatibility (Legacy)"],"parameters":[{"name":"id","in":"query","description":"ID of the successfully uploaded email list","required":true,"schema":{"type":"string","example":""}}],"responses":{"401":{"description":"Bearer token required (Authorization header)","content":{"application/json":{}}}},"externalDocs":{"api_ref":"https://emaillistverify.com/api#getApiFileInfo","api_endpoint":"https://api.emaillistverify.com/api/getApiFileInfo"},"summary":"Retrieve progress information of email list (getApiFileInfo)","description":"Retrieve progress information of email list | ## Retrieve progress information of email list\n#### Rate limit: 100 requests in 1 second\nThis endpoint furnishes progress updates for an uploaded email list encoded in plain text. Depending on the processing state of the email list, the response body may display:\n1. errored: An unknown error occurred during the verification of the email list. **No credits were deducted** for this email list.\n1. waiting: You have reached the maximum limit of concurrently verifying email lists. The email list will initiate automatically once some of the ongoing verifications are completed.\n1. &#124;<id>&#124;<filename>&#124;no&#124;<total_emails>&#124;<processed_emails>&#124;progress&#124;<created_timestamp>&#124;&#124;: The email list verification is in progress.\n1. &#124;<id>&#124;<filename>&#124;no&#124;<total_emails>&#124;<total_emails>&#124;finished&#124;<created_timestamp>&#124;<ok_url>&#124;<all_url>&#124;: The email list verification is finished.\nThe response bodies in steps 3 and 4 adhere to a custom format where the variables are defined as follows:\n- <id>: ID of the uploaded email list\n- <filename>: Name of the uploaded email list\n- <total_emails>: The total count of emails identified within the uploaded email list\n- <processed_emails>: Total count of emails that have already been verified\n- <created_timestamp>: Unix timestamp indicating the time of upload\n- <ok_url>: Download URL containing deduplicated emails with `ok` status\n- <all_url>: Download URL containing all emails and their corresponding statuses | Source: official OpenAPI spec at https://api.emaillistverify.com/api-doc","security":[{"bearerAuth":[]}]}}},"components":{"securitySchemes":{"bearerAuth":{"type":"http","scheme":"bearer"}}},"security":[{"bearerAuth":[]}]}