intercom / intercom-php
Intercom API client.
Installs: 19 020 297
Dependents: 29
Suggesters: 0
Security: 0
Stars: 301
Watchers: 192
Forks: 145
Open Issues: 39
pkg:composer/intercom/intercom-php
Requires
- php: ^8.1
- ext-json: *
- guzzlehttp/guzzle: ^7.4
Requires (Dev)
- friendsofphp/php-cs-fixer: 3.5.0
- phpstan/phpstan: ^1.12
- phpunit/phpunit: ^9.0
- dev-master
- 5.0.1
- v4.5.1
- v4.5.0
- 4.4.3
- v4.4.2
- v4.4.1
- v4.4.0
- v4.3.0
- v4.2.0
- v4.1.2
- v4.1.1
- v4.1.0
- v4.0.3
- v4.0.2
- v4.0.1
- v4.0.0
- v3.2.0
- v3.1.8
- v3.1.7
- v3.1.6
- v3.1.5
- v3.1.4
- v3.1.3
- v3.1.2
- v3.1.1
- v3.1.0
- v3.0.2
- v3.0.1
- v3.0.0
- v2.0.0
- v1.5.0
- v1.4.0
- v1.3.2
- v1.3.1
- v1.3.0
- v1.2.3
- v1.2.2
- v1.2.1
- v1.2.0
- v1.1.1
- v1.1.0
- v1.0.0
- v1.0.0-b12
- v1.0.0-b11
- v1.0.0-b10
- v1.0.0-b9
- v1.0.0-b8
- v1.0.0-b7
- v1.0.0-b6
- v1.0.0-b5
- v1.0.0-b4
- v1.0.0-b3
- v1.0.0-b2
- v1.0.0-b1
- dev-fern-bot/2025-09-11T21-46Z
- dev-df/test
- dev-ga/php-74
- dev-ga/raise-4xx-5xx-exceptions
- dev-ga/http-plug-56
- dev-mm/add_event_metadata
- dev-segment_readme
- dev-cho_bulk_url
- dev-AP/PHP-7
- dev-damon/updating-readme
- dev-bv/add_leads_scroll
- dev-lucianocn-master
- dev-timlim/add-visitors
- dev-timlim/readme-leads
- dev-anas/pagination-fixes
- dev-curtis/readme
- dev-amburke-delete-user
- dev-bulk-api-readme-code
- dev-BL/composer
- dev-MH/readme
- dev-jo/spec-server-error
- dev-jo/updateuserid
- dev-jo/add-signed-up-at
- dev-jo/add-admin-conversation-replies
- dev-update-last-request-at-json-for-create
- dev-jo/remove-admin_id-constraint-on-note
- dev-get-all-conversations
- dev-jo/beta-5-packagist
- dev-jo/add-remote-created-at
- dev-dehora/rm-3
This package is auto-updated.
Last update: 2025-10-08 13:47:14 UTC
README
The Intercom PHP library provides convenient access to the Intercom APIs from PHP.
Requirements
This SDK requires PHP ^8.1.
Installation
composer require intercom/intercom-php
Usage
Instantiate and use the client with the following:
<?php namespace Example; use Intercom\IntercomClient; use Intercom\AiContent\Requests\CreateContentImportSourceRequest; use Intercom\AiContent\Types\CreateContentImportSourceRequestStatus; $client = new IntercomClient( token: '<token>', ); $client->aiContent->createContentImportSource( new CreateContentImportSourceRequest([ 'syncBehavior' => 'api', 'status' => CreateContentImportSourceRequestStatus::Active->value, 'url' => 'url', ]), );
Exception Handling
When the API returns a non-success status code (4xx or 5xx response), an exception will be thrown.
use Intercom\Exceptions\IntercomApiException; use Intercom\Exceptions\IntercomException; try { $response = $client->aiContent->createContentImportSource(...); } catch (IntercomApiException $e) { echo 'API Exception occurred: ' . $e->getMessage() . "\n"; echo 'Status Code: ' . $e->getCode() . "\n"; echo 'Response Body: ' . $e->getBody() . "\n"; // Optionally, rethrow the exception or handle accordingly. }
Pagination
List endpoints return a Pager<T>
which lets you loop over all items and the SDK will automatically make multiple HTTP requests for you.
use Intercom\IntercomClient; $client = new IntercomClient( '<token>', ['baseUrl' => 'https://api.example.com'], ); $items = $client->articles->list(['limit' => 10]); foreach ($items as $item) { var_dump($item); }
You can also iterate page-by-page:
foreach ($items->getPages() as $page) { foreach ($page->getItems() as $pageItem) { var_dump($pageItem); } }
Legacy SDK
While the new SDK has a lot of improvements, we at Intercom understand that it takes time to upgrade when there are breaking changes.
To make the migration easier, the new SDK also exports the legacy SDK as Intercom\Legacy\...
. Here's an example of how you can use the
legacy SDK alongside the new SDK inside a single file:
use Intercom\IntercomClient; use Intercom\Legacy\IntercomClient as LegacyIntercomClient; $intercom = new IntercomClient(); $legacyClient = new LegacyIntercomClient();
We recommend migrating to the new SDK using the following steps:
-
Upgrade the package to
^5.1.0
-
Search and replace all requires and imports from
Intercom\...
toIntercom\Legacy\...
-
Gradually move over to use the new SDK by importing it from the
Intercom\...
import.
Advanced
Custom Client
This SDK is built to work with any HTTP client that implements Guzzle's ClientInterface
.
By default, if no client is provided, the SDK will use Guzzle's default HTTP client.
However, you can pass your own client that adheres to ClientInterface
:
use Intercom\IntercomClient; // Create a custom Guzzle client with specific configuration. $customClient = new \GuzzleHttp\Client([ 'timeout' => 5.0, ]); // Pass the custom client when creating an instance of the class. $client = new IntercomClient(options: [ 'client' => $customClient ]); // You can also utilize the same technique to leverage advanced customizations to the client such as adding middleware $handlerStack = \GuzzleHttp\HandlerStack::create(); $handlerStack->push(MyCustomMiddleware::create()); $customClient = new \GuzzleHttp\Client(['handler' => $handlerStack]); // Pass the custom client when creating an instance of the class. $client = new IntercomClient(options: [ 'client' => $customClient ]);
Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retryable when any of the following HTTP status codes is returned:
Use the maxRetries
request option to configure this behavior.
$response = $client->articles->create( ..., options: [ 'maxRetries' => 0 // Override maxRetries at the request level ] );
Timeouts
The SDK defaults to a 30 second timeout. Use the timeout
option to configure this behavior.
$response = $client->articles->create( ..., options: [ 'timeout' => 3.0 // Override timeout to 3 seconds ] );
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!