Download the PHP package jojostx/laravel-elasticemail without Composer

Table of Contents

• Overview
• Installation
  • Requirements
  • Install the Package
  • Publish the Config
  • Getting Your ElasticEmail API Key
• Usage
  • Methods
    • Validating One Email Address
    • Validating Multiple Email Addresses
  • Facade
  • Available Validation Result Properties
  • Caching
    • Caching Validation Results
    • Busting the Cached Validation Results
• Testing
• Security
• Contribution
• Credits
• Changelog
• License

Overview

Laravel ElasticEmail is a lightweight wrapper Laravel package that can be used for validating email addresses via the ElasticEmail API. The package supports caching so that you can start validating email addresses instantly.

Installation

Requirements

The package has been developed and tested to work with the following minimum requirements:

• PHP 8.0+
• Laravel 8+

Install the Package

You can install the package via Composer:

Publish the Config

You can then publish the package's config file (so that you can make changes to them) by using the following command:

Getting Your ElasticEmail API Key

To use this package and interact with the ElasticEmail API, you'll need to register on the ElasticEmail API website and get your API key. Once you have the key, you can set it in your .env file as shown below:

Usage

Methods

Validating One Email Address

To validate a single email address, you can use the check() method that is provided in the package. This method returns a ValidationResult object.

The example below shows how to validate a single email address:

Validating Multiple Email Addresses

To validate multiple email addresses, you can use the checkMany() method that is provided in the package. This method returns a Collection of ValidationResult objects.

The example below shows how to validate multiple email addresses:

Facade

If you prefer to use facades in Laravel, you can choose to use the provided ElasticEmail facade instead of instantiating the

class manually.

The example below shows an example of how you could use the facade to validate an email address:

Available Validation Result Properties

Caching

Caching Validation Results

There might be times when you want to cache the validation results for an email. This can have significant performance benefits for if you try to validate the email again, due to the fact that the results will be fetched from the cache rather than from a new API request.

As an example, if you were importing a CSV containing email addresses, you might want to validate each of the addresses. However, if the CSV contains some duplicated email addresses, it could lead to unnecessary API calls being made. So, by using the caching, each unique address would only be fetched once from the API. To do this, you can use the shouldCache() method.

Using caching is recommended as it reduces the chances of you reaching the monthly request limits or rate limits that are used by ElasticEmail. Read more about the API limits here.

The example below shows how to cache the validation results:

Busting the Cached Validation Results

By default, the package will always try to fetch the validation results from the cache before trying to fetch them via the API. As mentioned before, this can lead to multiple performance benefits.

However, there may be times that you want to ignore the cached results and make a new request to the API. As an example, you might have a cached validation result that is over 6 months old and could possibly be outdated or inaccurate, so it's likely that you want to update the validation data and ensure it is correct. To do this, you can use the fresh() method.

The example below shows how to fetch a new validation result:

Testing

Security

If you find any security related issues, please contact me directly at Jojostx to report it.

Contribution

If you wish to make any changes or improvements to the package, feel free to make a pull request.

To contribute to this library, please use the following guidelines before submitting your pull request:

• Write tests for any new functions that are added. If you are updating existing code, make sure that the existing tests pass and write more if needed.
• Follow PSR-2 coding standards.
• Make all pull requests to the branch.

Credits

• Jojostx
• All Contributors

Changelog

Check the CHANGELOG to get more information about the latest changes.

License

The MIT License (MIT). Please see License File for more information.