Download the PHP package kontent-ai/delivery-sdk-php without Composer

Kontent.ai Delivery SDK for PHP

Summary

The Kontent.ai Delivery PHP SDK is a client library used for retrieving content from Kontent.ai. The best way to use the SDK is to consume it in the form of a Packagist package. The library currently supports only PHP 8 and above.

Sample site

Check out a sample site running on Laravel utilizing this SDK here: https://github.com/kontent-ai/sample-app-php

Installation

The best way to install the client is through a dependency manager called Composer:

or adjusting your composer.json file:

Autoloading

Writing object-oriented applications requires one PHP source file per class definition. One of the biggest annoyances is having to write a long list of needed includes at the beginning of each script (one for each class).

Since the SDK uses Composer dependency manager and specifies autoload information, Composer generates a vendor/autoload.php file. You can simply include this file and start using the namespaces that those libraries offer without any extra work:

Using the DeliveryClient

The DeliveryClient class is the main class of the SDK. Using this class, you can retrieve content from your Kontent.ai projects.

To create an instance of the class, you need to provide a project ID.

There are some other optional parameters that you can use during the DeliveryClient instantiation.

• $previewApiKey – sets the Delivery Preview API key. The client will automatically start using the preview endpoint for querying. See previewing unpublished content.
• $securedProductionApiKey – sets the production Delivery API key (do not combine it with the Delivery Preview API key)
• $waitForLoadingNewContent – makes the client instance wait while fetching updated content, useful when acting upon webhook calls.
• $debugRequests – switches the HTTP client to debug mode
• $retryAttempts – number of times the client will retry to connect to the Kontent.ai API on failures per request

Once you create a DeliveryClient, you can start querying your project repository by calling methods on the client instance. See Basic querying for details.

Basic querying

Once you have a DeliveryClient instance, you can start querying your project repository by calling methods on the instance.

Filtering retrieved data

The SDK supports full scale of the API querying and filtering capabilities as described in the API reference.

Getting localized items

The language selection is just a matter of specifying one additional filtering parameter to the query.

Working with taxonomies

To retrieve information about your taxonomies, you can use the getTaxonomy and getTaxonomies methods. Additionally, you can specify query parameters.

Previewing unpublished content

To retrieve unpublished content, you need to create a DeliveryClient with both Project ID and Preview API key. Each Kontent.ai project has its own Preview API key.

For more details, see Previewing unpublished content using the Delivery API.

Response structure

For full description of single and multiple content item JSON response formats, see our API reference.

Single content item response

When retrieving a single content item, you get an instance of the ContentItem class. This class contains a 'system' property (with metadata about the content item, such as code name, display name, type, collection, or sitemap location) and respective content item's elements projected as camelCase properties.

Multiple content items response

When retrieving a list of content items, you get an instance of the ContentItemsResponse. This class represents the JSON response from the Delivery API endpoint and contains:

• Pagination property with information about the following:
  • Skip: requested number of content items to skip
  • Limit: requested page size
  • Count: the total number of retrieved content items
  • NextPageUrl: the URL of the next page
• An array of the requested content items

Properties and their types

• All properties are named in the camelCase style.
• If a property contains a collection of objects, it's typed as an array which is indexed by:
  • codenames, if the contained entities have a code name
  • numbers, if they don't have code names. We use zero-based indexing.
• If a property references linked items (property is of the linked item type), the references are replaced with the respective content items themselves.
• If a property is of asset, multiple choice option, or taxonomy group type, it's resolved to respective well-known models from the Kontent\Ai\Delivery\Models\Items namespace.
• All timestamps are typed as \DateTime.
• All numbers are typed as float.

Mapping custom models

It's possible to instruct the SDK to fill and return your own predefined models. To do that you have to implement:

• TypeMapperInterface (required) - to provide mapping of Kontent.ai content types to your models
• PropertyMapperInterface (optional) - to change the default behavior of property mapping (the default property translation works like this: 'content_type' -> 'contentType')
• ValueConverterInterface (optional) - to change the way content element types are mapped to PHP types
• ContentLinkUrlResolverInterface (optional) - to change the way the links in Rich text elements are resolved see Resolving links to content items.
• InlineLinkedItemsResolverInterface (optional) - to change the way content items in Rich text elements are resolved see Resolving content items and components in Rich text.

The default implementation of all the interfaces can be found in a class called DefaultMapper.

Example:

The ArticleModel can then look like this (and contain only the properties you need to work with):

Feedback & Contributing

Check out the contributing page to see the best places to file issues, start discussions, and begin contributing.

1. Clone the repository
2. Run composer install to install dependencies
3. Run phpunit to verify that everything works as expected

Developing on Windows

Have a look at our cool tutorial on developing PHP on Windows with Visual Studio Code!

Developing on Linux

Do you prefer penguins? Check out our tutorials on developing PHP on Linux with PhpStorm!

Wall of Fame

We would like to express our thanks to the following people who contributed and made the project possible:

• Stephen Rushing - eSiteful - ORIGINAL WORK

Would you like to become a hero too? Pick an issue and send us a pull request!