The ID of the email verification job to delete.

An input file containing the email addresses to verify.

By default, we use the MIME type returned with the file.

Advanced: the zero-based number of the first row to import and process; if not specified, we start from the first (0) row.

Advanced: the zero-based number of the last row to import and process; if not specified, we process rows until the end of the file.

Advanced: valid only for Plain Text and Delimiter-Separated Values files. By default, we attempt to guess the correct line ending.

Advanced: valid only for Delimiter-Separated Values files. By default, we use the comma symbol (,).

Advanced: valid only for Delimiter-Separated Values and Excel files. The zero-based index of the column to import. If not specified, we use the first (0) column.

Advanced: valid only for Excel files. The zero-based index of the worksheet to import. If not specified, we use the first (0) worksheet.

The higher the quality level the longer it could take to complete the verification. By default, we use the configured default quality level for your Verifalia user.

Choose whether / how we should mark duplicated email addresses.

The retention period to observe for the validation job, expressed in the format dd.hh:mm:ss (where dd: days, hh: hours, mm: minutes, ss: seconds); the initial dd. part is added only for periods of more than 24 hours. The value has a minimum of 5 minutes (0:5:0) and a maximum of 30 days (30.0:0:0): Verifalia will delete the job and its data once its data retention period is over, starting to count when it gets completed.

Query results must have a unique id field so we can deduplicate records properly! Otherwise we will make a best guess. You must also include desired ordering and limiting in the query.

Note: This query must run in less than 30 seconds and it is recommended that you return no more than 5,000 rows

Usually something auto-incremented like id. Must be unique. Column names that contain a space must be enclosed within brackets [ ].

Usually something like date_updated or last_modified. This should ideally be a datetime column that is set to the current datetime whenever a row is updated.

Trigger on changes to cells in this column only. Leave blank if you want to trigger on changes to cells in all columns.

The higher the quality level the longer it could take to complete the verification. By default, we use the configured default quality level for your Verifalia user.

The retention period to observe for the validation job, expressed in the format dd.hh:mm:ss (where dd: days, hh: hours, mm: minutes, ss: seconds); the initial dd. part is added only for periods of more than 24 hours. The value has a minimum of 5 minutes (0:5:0) and a maximum of 30 days (30.0:0:0): Verifalia will delete the job and its data once its data retention period is over, starting to count when it gets completed.

No setup is required for this action.

We expect at least one unique (and usually autoincrement) primary key column so we can deduplicate records properly! Otherwise we will make a best guess on a random column to use to deduplicate.

Highly recommended! Usually you want the results to be most recent first so we can skim off only new results, so choose something like date_created or your autoincrement id. Column names that contain a space must be enclosed within brackets [ ].

We default to what the primary key is on the table as the unique key to deduplicate on. If you prefer another field, select it here.