The Apigee API Client Library for PHP makes it easy to develop PHP clients that call the Apigee Edge/ X Management API. The Apigee API Client Library for PHP enables you to interact with the API using objects instead of coding to handle the HTTP request and response calls directly.
Specifically, the Apigee API Client Library for PHP provides access to Apigee Edge and Apigee Management APIs in the following categories:
- API Products
- Apps
- Apps: Company
- Apps: Developer
- Companies
- Company App Keys
- Company Developers
- Developer App Keys
- Developers
- Stats
- API Products
- Apps
- Apps: AppGroup
- Apps: Developer
- AppGroup
- AppGroup App Keys
- Developer App Keys
- Developers
- Stats
For more information about the Apigee Edge and Apigee Management APIs, see Getting started with the Apigee Edge Management APIs and Getting started with the Apigee Management APIs in the Apigee documentation.
The Apigee API Client Library for PHP, built using the HTTPlug library, provides an HTTP client implementation-independent library. You choose the client that best fits your project requirements.
If you need PHP < 7.1 or Monetization API support please install the older edge-php-sdk version. We are planning to add Monetization API support to this library in the near future.
Core Persistent Services (CPS) is not available on Private Cloud installations.
The PHP API client supports pagination on listing API endpoints (ex.: List Developers). If CPS is not available the PHP API client simulates the pagination feature and it triggers an E_USER_NOTICE level error to let developers know that the paginated result is generated by PHP and not the Management API server.
This notice can be suppressed in multiple ways. You can suppress it by changing PHP's error_reporting configuration to
suppress all E_NOTICE level errors with changing its value to E_ALL | ~E_NOTICE for example. You can also suppress only the notice generated by the PHP API client by setting the APIGEE_EDGE_PHP_CLIENT_SUPPRESS_CPS_SIMULATION_NOTICE environment variable value to a falsy value, for example: APIGEE_EDGE_PHP_CLIENT_SUPPRESS_CPS_SIMULATION_NOTICE=1.
Support for Apigee hybrid API has been added to this library and is now considered to be production ready. If you run into any problems, add an issue to our GitHub issue queue.
You must install an HTTP client or adapter before you install the Apigee API Client Library for PHP. For a complete list of available clients and adapters, see Clients & Adapters in the PHP-HTTP documentation.
To install the client library using Guzzle 6, enter the following commands:
$ composer require php-http/guzzle6-adapter:^1.1.1
$ composer require apigee/apigee-client-php
<?php
use Apigee\Edge\Api\Management\Controller\DeveloperController;
use Apigee\Edge\Api\Management\Entity\Developer;
use Apigee\Edge\Exception\ApiException;
use Apigee\Edge\Exception\ClientErrorException;
use Apigee\Edge\Exception\ServerErrorException;
use Apigee\Edge\Client;
use Http\Message\Authentication\BasicAuth;
include_once 'vendor/autoload.php';
$username = '[email protected]';
$password = 'my-secure-password';
$organization = 'my-organization';
$auth = new BasicAuth($username, $password);
// Initialize a client and use basic authentication for all API calls.
$client = new Client($auth);
// Initialize a controller for making API calls, for example a developer controller to working with developer entities.
$ec = new DeveloperController($organization, $client);
try {
/** @var \Apigee\Edge\Api\Management\Entity\Developer $entity */
$entity = $ec->load('[email protected]');
$entity->setEmail('[email protected]');
$ec->update($entity);
// Some setters on entities are intentionally marked as @internal because the underlying entity properties can not
// be changed on the entity level. Those must be modified by using dedicated API calls.
// So instead of this:
$entity->setStatus(Developer::STATUS_INACTIVE);
// You should use this:
$ec->setStatus($entity->id(), Developer::STATUS_INACTIVE);
} catch (ClientErrorException $e) {
// HTTP code >= 400 and < 500. Ex.: 401 Unauthorised.
if ($e->getEdgeErrorCode()) {
print $e->getEdgeErrorCode();
} else {
print $e;
}
} catch (ServerErrorException $e) {
// HTTP code >= 500 and < 600. Ex.: 500 Server error.
} catch (ApiException $e) {
// Anything else, because this is the parent class of all the above.
}- Create new developer app with a custom- and an auto-generated credential
- Developer app analytics
- List entities (developers, api products, developer apps, etc.)
Setup the test suite using Composer if it has not already done:
$ composer install --dev
Run it using PHPUnit:
$ composer test
Testing of new changes does not require Apigee Edge connection. By default, unit tests are using the content of the offline-test-data folder to make testing quicker and easier. If you would like to run units tests with a real Apigee Edge instance you have to specify the following environment variables (without brackets):
APIGEE_EDGE_PHP_CLIENT_API_CLIENT=\Apigee\Edge\Tests\Test\Client
APIGEE_EDGE_PHP_CLIENT_HTTP_CLIENT=\Http\Adapter\Guzzle6\Client
APIGEE_EDGE_PHP_CLIENT_BASIC_AUTH_USER=[[email protected]]
APIGEE_EDGE_PHP_CLIENT_BASIC_AUTH_PASSWORD=[PASSWORD]
APIGEE_EDGE_PHP_CLIENT_ORGANIZATION=[ORGANIZATION]
APIGEE_EDGE_PHP_CLIENT_ENVIRONMENT=[ENVIRONMENT]
# If test organization does not support CPS.
APIGEE_EDGE_PHP_CLIENT_SUPPRESS_CPS_SIMULATION_NOTICE=1There are multiple ways to set these environment variables, but probably the easiest is creating a copy from the
phpunit.xml.dist file as phpunit.xml and uncomment the env elements inside the element.
It is also possible to create and use your own data set. If you would like to use your own offline test data set then
you just need to define the APIGEE_EDGE_PHP_CLIENT_OFFLINE_TEST_DATA_FOLDER environment variable set its value to the parent
folder of your own test data set.
PS.: Some unit tests cannot be executed when the offline test data set is in use, those are automatically marked as skipped.
This library follows the Semantic Versioning strategy. It means only major releases (such as 3.0, 4.0 etc.) are allowed to break backward compatibility and we do our best to keep it this way. The PHP API Client has to be compatible with the latest versions of the supported Apigee Edge APIs. As you can see, almost every class implements at least one interface in this library, therefore, we would like to suggest to rely on interface definitions instead of concrete classes if you build something on the top of this library. Also, prefer encapsulation over inheritance if you extend our classes. We will release a new major version from this library if a change in a supported Apigee Edge API cannot be implemented in the PHP API client without changing an interface.
This project, which connects Drupal 8 with Apigee Edge, is supported by Google. Use our project's issue queue to report any questions, issues, or feedback.
We would love to accept contributions to this project, please see the contribution guidelines for this project for more details.