The Kontent.ai Delivery Java SDK is a client library used for retrieving content from Kontent.ai.
You can use the SDK in the form of a Apache Maven package from Maven Central - so you need to point your Maven to mavenCentral
repositories {
mavenCentral()
}
dependencies {
implementation 'ai.kontent:delivery-sdk:latest.release'
}
You may want to change
latest.release
to specific one (i.e.5.0.0
).
<dependency>
<groupId>ai.kontent</groupId>
<artifactId>delivery-sdk</artifactId>
<version>[5.0.0,)</version>
<type>pom</type>
</dependency>
You may want to change version specification -
[5.0.0,)
- from range one to specific one (i.e.5.0.0
).
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.
// Initializes an instance of the DeliveryClient client
DeliveryClient client = new DeliveryClient("975bf280-fd91-488c-994c-2f04416e5ee3");
You can also provide the project ID and other parameters by passing the DeliveryOptions
object to the class constructor. The DeliveryOptions
object can be used to set the following parameters:
setPreviewApiKey(String)
– sets the Delivery Preview API key.setProductionApiKey(String)
- sets the Delivery Client key for secured access.setProjectId(String)
– sets the project identifier.setUsePreviewApi(boolean)
– determines whether to use the Delivery Preview API.setWaitForLoadingNewContent(boolean)
– makes the client instance wait while fetching updated content, useful when acting upon webhook calls.setRetryAttempts(int)
- sets the number of retry attempts the client should make when a request to the API fails.setProductionEndpoint(String)
- sets the production endpoint address. Mainly useful to change for mocks in unit tests, or if you are establishing a proxy.setPreviewEndpoint(String)
- sets the preview endpoint address. Mainly useful to change for mocks in unit tests, or if you are establishing a proxy.setProxyServer(java.net.Proxy)
- sets the proxy server used by the http client. Mainly used to complex Proxy scenarios.setCustomHeaders(java.utils.List<Header>)
- sets custom headers to be included in the request. Check the reserved header names in method remarks. These will be ignored.
The DeliveryOptions.builder()
can also simplify creating a DeliveryClient
:
DeliveryClient client = new DeliveryClient(
DeliveryOptions
.builder()
.projectId("975bf280-fd91-488c-994c-2f04416e5ee3")
.productionApiKey("secured key")
.build()
);
Once you create a DeliveryClient
, you can start querying your project repository by calling methods on the client instance. See Basic querying for details.
To retrieve unpublished content, you need to create a DeliveryClient
with both Project ID and Preview API key (You could also configure Preview API key in DeliveryOptions
described above). Each Kontent.ai project has its own Preview API key.
// Note: Within a single project, we recommend that you work with only
// either the production or preview Delivery API, not both.
DeliveryClient client = new DeliveryClient(
"YOUR_PROJECT_ID",
"YOUR_PREVIEW_API_KEY"
);
For more details, see Previewing unpublished content using the Delivery API.
Once you have a DeliveryClient
instance, you can start querying your project repository by calling methods on the instance.
// Retrieves a single content item
CompletionStage<ContentItemResponse> response = client.getItem("about_us");
// Retrieves a list of all content items
CompletionStage<ContentItemsListingResponse> listingResponse = client.getItems();
As you may have noticed from the example DeliveryClient
is returning CompletionStage<T>
that allows you to chain the requests, perform filtering, data transformation, etc.
Sometimes, it is necessary to transform asynchronous calls CompletionStage<T>
to synchronous ones and return the data (T
).
Keep in mind this transformation needs to handle possible
ExecutionException
andInterruptedException
that could be raised when waiting to process the transformation.
// Retrieves a single content item
ContentItemResponse response = client.getItem("about_us")
.toCompletableFuture()
.get();
// Retrieves a list of all content items
ContentItemsListingResponse listingResponse = client.getItems()
.toCompletableFuture()
.get();
The SDK supports full scale of the API querying and filtering capabilities as described in the API reference.
// Retrieves a list of the specified elements from the first 10 content items of
// the 'brewer' content type, ordered by the 'product_name' element value
// also includes total number of items stored in Kontent.ai i.e. for pagination purposes
CompletionsStage<ContentItemsListingResponse> response = client.getItems(
DeliveryParameterBuilder.params()
.language("es-ES")
.filterEquals("system.type", "brewer")
.projection("image", "price", "product_status", "processing")
.page(null, 10)
.orderByAsc("elements.product_name")
.includeTotalCount()
.build()
)
For full description of single and multiple content item JSON response formats, see our API reference.
When retrieving a single content item, you get an instance of the ContentItemResponse
class. This class represents the JSON response from the Delivery API endpoint and contains the requested ContentItem
as a property.
When retrieving a list of content items, you get an instance of the ContentItemsListingResponse
. This class represents the JSON response from the Delivery API endpoint and contains:
getPagination()
returns aPagination
object with information about the following:getSkip()
: requested number of content items to skipgetLimit()
: requested page sizegetCount()
: the total number of retrieved content itemsgetTotalCount()
: total number of content items matching the search criteriagetNextPage()
: the URL of the next page
- A list of the requested content items
The ContentItem
class provides the following:
getSystem()
returns aSystem
object with metadata such as code name, display name, type, collection, sitemap location, or workflow step.getElements()
returns a Map containing all the elements included in the response keyed by code names.- Methods for easier access to certain types of content elements such as linked items, or assets.
You can access information about a content item (i.e., its ID, codename, name, location in sitemap, date of last modification, its collection codename, and its content type codename) by using the System
object.
// Retrieves name of an article content item
articleItem.getSystem().getName()
// Retrieves codename of an article content item
articleItem.getSystem().getCodename()
// Retrieves codename of the collection of an article content item
articleItem.getSystem().getCollection()
// Retrieves codename of the content type of an article content item
articleItem.getSystem().getType()
// Retrieves codename of the workflow step of an article content item
articleItem.getSystem().getWorkflowStep()
The SDK provides methods for retrieving content from content elements such as Asset, Text, Rich Text, Multiple choice, etc.
For text elements, you can use the getString
method.
// Retrieves an article text from the 'body_copy' Text element
articleItem.getString("body_copy")
The Rich text element can contain links to other content items within your project. See Resolving links to content items for more details.
// Retrieves a teaser image URL
articleItem.getAssets("teaser_image").get(0).getUrl()
To get a list of options defined in a Multiple choice content element, you first need to retrieve the content element itself. For this purpose, you can use the getContentTypeElement
method, which takes the codename of a content type and the codename of a content element.
// Retrieves the 'processing' element of the 'coffee' content type
MultipleChoiceElement element = (MultipleChoiceElement) client.getContentTypeElement("coffee", "processing");
After you retrieve the Multiple choice element, you can work with its list of options. Each option has the following methods:
Method | Description | Example |
---|---|---|
getName() | The display name of the option. | Dry (Natural) |
getCodename() | The codename of the option. | `dry__natural_ |
To put the element's options in a list, you can use the following code:
List<SelectListItem> items = new List<>();
for (Option option : element.getOptions()) {
SelectListItem item = new SelectListItem();
item.setText(option.getName());
item.setValue(option.getCodename());
item.setSelected("semi_dry".equals(option.getCodename()));
}
// Retrieves related articles
articleItem.getLinkedItems("related_articles")
// Retrieves the value of the custom element 'color'
String customElementValue = ((CustomElement) articleItem.getElements().get("color")).getValue();
To use this SDK for Android development, you can use any approach compatible with Java CompletionStage API. Most common is to use Kotlin coroutines for Android applications written in Kotlin and Java RX for Android applications written in Java. Both of these approaches are showcased in this repository:
⚠ There are two Android-specific rules you need to follow in order for the Delivery SDK to work correctly.
- Disable template engine integration when initializing the Delivery client.
- Avoid using the
scanClasspathForMappings
method.
You need to instantiate the Delivery client with the constructor that disables the template engine. The template engine is meant to be used with the web platform only. For Android development, use the constructor DeliveryClient#DeliveryClient(DeliveryOptions, TemplateEngineConfig)
and set the second parameter to null
.
DeliveryClient client = new DeliveryClient(new DeliveryOptions(AppConfig.KONTENT_PROJECT_ID), null);
See it used in a sample app).
Android applications must register the models using the registerType
method. See a usage example in DeliveryClientProvider.java.
You can still use the model generator for generating the models.
⚠ The
scanClasspathForMappings
method does not work in the Android environment. Because of the differences between Android Dalvik VM and Java VM, the scanning library is not usable here. That's why you need to use theregisterType
method instead.
To see more detailed information, check out the Kontent.ai Java packages documentation section.
For more developer resources, visit the Kontent.ai Learn portal.
If you want to explore the possibilities of the SDK, visit Features section of the Spring boot application.
Check out the contributing page to see the best places to file issues, start discussions, and begin contributing.
We would like to express our thanks to the following people who contributed and made the project possible:
Would you like to become a hero too? Pick an issue and send us a pull request!