Download the PHP package joinposter/intercom-integration-php without Composer

intercom-php

Official PHP bindings to the Intercom API

Installation

This library supports PHP 7.1 and later

This library uses HTTPlug as HTTP client. HTTPlug is an abstraction that allows this library to support many different HTTP Clients. Therefore, you need to provide it with an adapter for the HTTP library you prefer. You can find all the available adapters in Packagist. This documentation assumes you use the Guzzle6 Client, but you can replace it with any adapter that you prefer.

The recommended way to install intercom-php is through Composer:

Clients

Initialize your client using your access token:

If you already have an access token you can find it here. If you want to create or learn more about access tokens then you can find more info here.

If you are building a third party application you can get your OAuth token by setting-up-oauth for Intercom.

For most use cases the code snippet above should suffice. However, if needed, you can customize the Intercom client as follows:

API Versions

This library is intended to work with any API Version. By default, the version that you have configured for your App in the Developer Hub will be used. However, you can overwrite that version for a single request or for all the requests using this library by including the Intercom-Version header when initializing the client as follows:

For more information about API Versioning, please check the API Versioning Documentation and the API changelog.

Users

Important: Not all the resources supported by this API are supported by all API versions. See the notes below or the API Reference for more information about the resources supported by each API version.

Contacts

This resource is only available in API Versions 2.0 and above

Users

This resource is only available in API Versions 1.0 to 1.4. Newer versions use the Contacts resource instead.

See here for more info on using the scroll parameter

Leads

This resource is only available in API Versions 1.0 to 1.4. Newer versions use the Contacts resource instead.

See here for more info on using the scroll parameter

Visitors

Retrieve user_id of a visitor via the JavaScript API

Tags

Segments

Events

Companies

Admins

Messages

Conversations

Counts

Notes

Teams

Rate Limits

Rate limit info is passed via the rate limit headers. You can access this information as follows:

For more info on rate limits and these headers please see the API reference docs

Pagination

When listing, the Intercom API may return a pagination object:

You can grab the next page of results using the client:

In API versions 2.0 and above subsequent pages for listing contacts can be retreived with:

Scroll

The first time you use the scroll API you can just send a simple GET request. This will return up to 100 records. If you have more than 100 you will need to make another call. To do this you need to use to scroll_parameter returned in the original response. Use this for subsequent responses until you get an empty array of records. This means there are no records and the scroll timer will be reset. For more information on scroll please see the API reference Here is an example of a simple way to use the scroll for multiple calls:

Exceptions

Exceptions are handled by HTTPlug. Every exception thrown implements Http\Client\Exception. See the http client exceptions and the client and server errors. The Intercom API may return an unsuccessful HTTP response, for example when a resource is not found (404). If you want to catch errors you can wrap your API call into a try/catch block:

Pull Requests

• Add tests! Your patch won't be accepted if it doesn't have tests.

• Document any change in behaviour. Make sure the README and any other relevant documentation are kept up-to-date.

• Create topic branches. Don't ask us to pull from your master branch.

• One pull request per feature. If you want to do more than one thing, send multiple pull requests.

• Send coherent history. Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before sending them to us.