PHP client to interact with Bee's plugin API

0.3.1 2022-01-25 11:50 UTC

This package is auto-updated.

Last update: 2024-03-15 22:07:35 UTC


Latest Version on Packagist Actions Status MIT Licensed StyleCI Total Downloads

PHP client to interact with Bee's plugin API. This includes the Message Services API and a convenient way to use authorization.


You can install the package via composer:

composer require kirschbaum-development/bee-plugin-php-client


First thing you will need is to instantiate the Bee base class and setup the API token. You can grab the API token by logging in into the Developer portal and going to the "details" of your application.

use KirschbaumDevelopment\Bee\Bee;

$bee = new Bee(new \GuzzleHttp\Client);

Using Message Services API: HTML

This API allows you to post the JSON content generated on the Bee editor, and it will return the rendered HTML of the JSON. Reference:

$beeEditorData = []; // this will be the JSON generated using the editor
$html = $bee->html($beeEditorData);

Using Message Services API: PDF

This API allows you to post the HTML content and get an URL with a PDF created from the HTML. Reference:

$pdf = $bee->pdf([
    'html' => $html, // HTML generated using the HTML API (required)
    'page_size' => 'Letter', // (optional)
    'page_orientation' => 'Landscape', // (optional)

// then, you can call these methods:

Using Message Services API: Image

This API allows you to post the HTML content and get an URL with a PDF created from the HTML. Reference:

$image = $bee->image([
    'html' => $html, // HTML generated using the HTML API (required)
    'width' => 500, // (required)
    'height' => 400, // (optional)
    'file_type' => 'jpg',

// then, you can save the image content somewhere, some examples on how you may do this:
file_put_contents('/path/to/storage/image.jpg', $image);

// on Laravel with Storage object:
Storage::put('/path/to/storage/image.jpg', $image);

Generating access token

To initialize Bee Editor you may need an access token. You can use BeeAuth to easily generate that. You can grab the Client ID and Secret by logging in into the Developer portal and going to the "details" of your application.

use KirschbaumDevelopment\Bee\BeeAuth;

$beeAuth = new BeeAuth(new \GuzzleHttp\Client);
$token = $beeAuth->generateToken();

// then you can use the following methods:

Auth tokens are valid for 5 minutes. If you want to cache your tokens for as long as possible, you will need to pass a PSR-16 compatible cache implementation. Laravel, Symfony and all major frameworks are already compatible with this interface. To enable the cache, you only need to call the setCache method passing a Psr\SimpleCache\CacheInterface implementation.


Usage with Laravel

If you use Laravel, BeePluginServiceProvider will be auto-registered if you use Laravel package discovery. Otherwise, you can manually register the following provider:

'providers' => [
    // ...

This will make sure that any time you ask Laravel for KirschbaumDevelopment\Bee\Bee or KirschbaumDevelopment\Bee\BeeAuth using the Laravel container (e.g. app(Bee::class)), Guzzle will be automatically injected and also the API token and Client ID/Secret will be injected into the classes.

The config values will be extracted from the following config: .services.bee. So, we'll use the following conventions:

API Token: config('services.bee.api_token') Client ID: config('services.bee.client_id') Client Secret: config('services.bee.client_secret')

If you don't want to use this config, you can always pass the values manually.

Caching with Laravel

Laravel service provider will also automatically inject Laravel's cache implementation on BeeAuth, so your auth tokens will be cached for as long as possible.

Testing with Laravel

If you are writing integration tests, but don't want your tests making requests to Bee to get credentials, we have a little helper that can help you. Just run the following code:

use KirschbaumDevelopment\Bee\Laravel\BeeAuthMock;


With this, any time you call BeeAuth::generateToken() in your code you will receive the same response you would receive, but with some fake tokens and without making any HTTP requests.


composer test


Please see CONTRIBUTING for details.


If you discover any security related issues, please email or instead of using the issue tracker.



Development of this package is sponsored by Kirschbaum Development Group, a developer driven company focused on problem solving, team building, and community. Learn more about us or join us!


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