Download the PHP package ezknock/ezknock-php-sdk without Composer

ezknock-php-sdk

Official PHP bindings to the EZ Knock API

Project Updates

Installation

This library supports PHP 7.3 and later

This library uses HTTPlug as HTTP client. HTTPlug is an abstraction that allows this library to support many different HTTP Clients. Therefore, you need to provide it with an adapter for the HTTP library you prefer. You can find all the available adapters in Packagist. This documentation assumes you use the Guzzle7 Client, but you can replace it with any adapter that you prefer.

The recommended way to install ezknock-php-sdk is through Composer:

Clients

Initialize your client using your access token:

If you already have an access token you can find it here. If you want to create or learn more about access tokens then you can find more info here.

For most use cases the code snippet above should suffice. However, if needed, you can customize the EZKnock client as follows:

Use a custom HTTP client

This client needs to implement Psr\Http\Client\ClientInterface

Use a custom request factory

This factory needs to implement Http\Message\RequestFactory

Use a custom URI factory

This factory needs to implement Http\Message\UriFactory

Coverage

Get coverage information by Zip code.

Create order

Create an order

Rate Limits

Rate limit info is passed via the rate limit headers. You can access this information as follows:

For more info on rate limits and these headers please see the API reference docs

Pagination

When listing, the EZ Knock API may return a pagination object:

You can grab the next page of results using the client:

Exceptions

Exceptions are handled by HTTPlug. Every exception thrown implements Http\Client\Exception. See the http client exceptions and the client and server errors. The EZ Knock API may return an unsuccessful HTTP response, for example when a resource is not found (404). If you want to catch errors you can wrap your API call into a try/catch block:

Pull Requests

• Add tests! Your patch won't be accepted if it doesn't have tests.

• Document any change in behaviour. Make sure the README and any other relevant documentation are kept up-to-date.

• Create topic branches. Don't ask us to pull from your master branch.

• One pull request per feature. If you want to do more than one thing, send multiple pull requests.

• Send coherent history. Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before sending them to us.