sendinblue/api-bundle

Symfony bundle for sendinblue/api-v3-sdk

This package will be archived on 31st October 2020 at 00:00:00 UTC., _(*1)

sendinblue/api-bundle

This bundle integrates sendinblue/api-v3-sdk into Symfony., _(*2)

Installation

Step 1: Download the Bundle

Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:, _(*3)

$ composer require sendinblue/api-bundle "~1"

This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation., _(*4)

Step 2: Enable the Bundle

Then, enable the bundle by adding it to the list of registered bundles in the app/AppKernel.php file of your project:, _(*5)

<?php
// app/AppKernel.php

// ...
class AppKernel extends Kernel
{
    public function registerBundles()
    {
        $bundles = array(
            // ...

            new SendinBlue\Bundle\ApiBundle\SendinBlueApiBundle(),
        );

        // ...
    }

    // ...
}

Configuration

sendinblue_api:
    endpoints: []
    key: ~

You’ll define the API client key under sendinblue_api.key., _(*6)

Then you’ll need to otp-in for the endpoints you want to access. One service will be created per endpoint:, _(*7)

• account
• attributes
• contacts
• email_campaigns
• folders
• lists
• process
• reseller
• senders
• sms_campaigns
• smtp
• transactional_sms
• webhooks

The service names will be sendinblue_api.%s_endpoint where %s is a value from the list above. The corresponding classes can be found under the SendinBlue\Client\Api namespace., _(*8)

/** @var SendinBlue\Client\Api\AccountApi $accountEndpoint */
$accountEndpoint = $this->get('sendinblue_api.account_endpoint');

Multiple clients

To use more than one client you must move key and endpoints parameter under a clients associative array. Each client will be named by its key., _(*9)

sendinblue_api:
    clients:
        first:
            endpoints:
                - account
            key: ~
        second:
            endpoints:
                - account
            key: ~

To access the first client account endpoint you’ll get the sendinblue_api.first_client.account_endpoint service., _(*10)

Default client

You can define a default client through the default_client parameter; by default it is the first defined client. You can access the default client endpoints without adding its name in the service name. In the above example the sendinblue_api.account_endpoint service would be an alias of sendinblue_api.first_client.account_endpoint., _(*11)

If you write, _(*12)

sendinblue_api:
    default_client: second
    clients:
        first:
            endpoints:
                - account
            key: ~
        second:
            endpoints:
                - account
            key: ~

then sendinblue_api.account_endpoint will be an alias of sendinblue_api.second_client.account_endpoint., _(*13)