Idiomatic PHP client for Google Cloud Platform services.

View the list of supported APIs and Services.

If you need support for other Google APIs, please check out the Google APIs Client Library for PHP.

We recommend installing individual component packages. A list of available packages can be found on Packagist.

For example:

$ composer require google/cloud-storage
$ composer require google/cloud-bigquery
$ composer require google/cloud-datastore

In this guide we'll focus on how to configure your client for local development using the Google Cloud CLI (gcloud).

• Install the Google Cloud CLI.
• Authenticate with gcloud to generate the credentials file.
• Instantiate a client.

In order to generate our needed credentials file we need to authenticate to gcloud first. Installation is handled differently depending on your platform. Here is a link to help you setup the Google Cloud CLI:

https://cloud.google.com/sdk/docs/install

Once the Google Cloud CLI tools are installed it is required that we authenticate via the gcloud:

$ gcloud init
$ gcloud auth application-default login

This will create a local file in your system that the authentication library for our client will read in order to make requests to the apis with those credentials. This file is located in different place depending on your system.

Windows:

%APPDATA%\gcloud\application_default_credentials.json

Linux and MacOS:

$HOME/.config/gcloud/application_default_credentials.json

To read more about Authentication, see AUTHENTICATION.md

Install the Google Translate client library with composer

composer install google/cloud-translate

Note: For this example, we are using the Google Translate client library. Check the the complete list of packages to find your required library.

Now that we've authenticated and installed the client library, we can instantiate a client which will detect the JSON file created by the gcloud CLI and use it to authenticate your requests:

require_once 'vendor/autoload.php';

use Google\Cloud\Translate\V3\Client\TranslationServiceClient;
use Google\Cloud\Translate\V3\TranslateTextRequest;

// Instantiating the client gathers the credentials from the `application_default_credentials.json`
$client = new TranslationServiceClient([]);

$request = new TranslateTextRequest();
$request->setParent('projects/<YOUR_PROJECT_ID>');
$request->setTargetLanguageCode('en-US');
$request->setContents(['こんにちは']);

// The request will contain the authentication token based on the default credentials file
$response = $client->translateText($request);

var_dump($response->getTranslations()[0]);
// {
//     ["translatedText"]=>
//     string(5) "Hello"
//     ["detectedLanguageCode"]=>
//     string(2) "ja"
// }

See Authentication for details and examples.

Please see our Debugging guide for more information about the debugging tools.

Many clients in Google Cloud PHP offer support for gRPC, either as an option or a requirement. gRPC is a high-performance RPC framework created by Google. To use gRPC in PHP, you must install the gRPC PHP extension on your server. While not required, it is also recommended that you install the protobuf extension whenever using gRPC in production.

$ pecl install grpc
$ pecl install protobuf

See Installing gRPC and Protobuf for a complete guide.

By default the library will use a simple in-memory caching implementation, however it is possible to override this behavior by passing a PSR-6 caching implementation in to the desired client.

The following example takes advantage of Symfony's Cache Component.

require 'vendor/autoload.php';

use Google\Cloud\Storage\StorageClient;
use Symfony\Component\Cache\Adapter\ArrayAdapter;

// Please take the proper precautions when storing your access tokens in a cache no matter the implementation.
$cache = new ArrayAdapter();

$storage = new StorageClient([
    'authCache' => $cache
]);

This library provides a PSR-6 implementation with the SystemV shared memory at Google\Auth\Cache\SysVCacheItemPool. This implementation is only available on *nix machines, but it's the one of the fastest implementations and you can share the cache among multiple processes. The following example shows how to use it.

require __DIR__ . '/vendor/autoload.php';

use Google\Cloud\Spanner\SpannerClient;
use Google\Auth\Cache\SysVCacheItemPool;

$cache = new SysVCacheItemPool();

$spanner = new SpannerClient([
    'authCache' => $cache
]);

To protect against the "Store Now, Decrypt Later" attack, Google Cloud is implementing Post-Quantum Cryptography (PQC) across its services.

For more information on Google Cloud's approach, see Post-Quantum Cryptography on Google Cloud.

Google Cloud client libraries support post-quantum key exchange using the X25519MLKEM768 hybrid mechanism for TLS 1.3 connections.

The grpc PHP extension statically bundles BoringSSL. Beginning with grpc v1.83.0, BoringSSL natively supports and advertises the X25519MLKEM768 hybrid group by default during TLS 1.3 handshakes.

• Configuration: No code changes, compilation flags, or environment variables are required.

• Verification: Confirm that your installed grpc extension version is 1.83.0 or higher:

  php -r "echo phpversion('grpc') . PHP_EOL;"

• Fallback: If connecting to an endpoint that does not support PQC, the handshake automatically falls back to classical X25519.

For clients configured to use the REST transport via Guzzle and cURL, key exchange negotiation relies on the host system's OpenSSL library linked to PHP's curl extension.

Requirements:

• OpenSSL 3.5.0 or higher: OpenSSL 3.5.0 introduced native support for X25519MLKEM768 and enabled it by default in TLS 1.3 supported groups.

• Verification: Ensure PHP's ext-curl is linked to OpenSSL 3.5.0+, not an older system default:

  php -r "echo curl_version()['ssl_version'] . PHP_EOL;"

• Fallback: Guzzle inherits default curve preferences from the underlying TLS library. If OpenSSL 3.5+ is present, X25519MLKEM768 is preferred automatically, falling back gracefully to standard X25519 when unsupported by the peer.

All client libraries support PHP 8.2 and above.

This library follows Semantic Versioning.

Please note it is currently under active development. Any release versioned 0.x.y is subject to backwards incompatible changes at any time.

GA: Libraries defined at a GA quality level are stable, and will not introduce backwards-incompatible changes in any minor or patch releases. We will address issues and requests with the highest priority. Please note, for any components which include generated clients the GA guarantee will only apply to clients which interact with stable services. For example, in a component which hosts V1 and V1beta1 generated clients, the GA guarantee will only apply to the V1 client as the service it interacts with is considered stable.

Beta: Libraries defined at a Beta quality level are expected to be mostly stable and we're working towards their release candidate. We will address issues and requests with a higher priority.

Contributions to this library are always welcome and highly encouraged.

See CONTRIBUTING for more information on how to get started.

This repository is not an official support channel. If you have support questions, file a support request through the normal Google support channels, or post questions on a forum such as StackOverflow.

Apache 2.0 - See LICENSE for more information.