Brightspot CMS Developer Guide
Brightspot CMS Developer Guide
Developer guide
Content Delivery API

Custom Content Delivery API development

Overview of custom CDA development
For stable production functionality, it typically makes more sense to build a custom Content Delivery endpoint via code, rather than entirely through editorial configuration. An endpoint class can ensure that a fixed set of APIs are exposed with configuration that should not change between different environments.

Implementing custom CDAs

  1. Create a new Java class extending ContentDeliveryApiEndpoint.
  2. Implement required methods:

  • getPathSuffix—appended to /graphql/delivery/ to create the path where the API endpoint is available.
  • getQueryEntryFields—objects wrapping view model and interface classes used to generate the schema and expose APIs.


public class FooContentDeliveryApiEndpoint extends ContentDeliveryApiEndpoint {

    protected String getPathSuffix() {
        return "foo"; // API endpoint is available at path '/graphql/delivery/foo'

    public List<ContentDeliveryEntryPointField> getQueryEntryFields() {
        return Arrays.asList(
               new ContentDeliveryEntryPointField(FooViewModel.class),
               new ContentDeliveryEntryPointField(BarViewModel.class));

Previous Topic
CDA guides
Next Topic
Using Brightspot GraphQL Preview
Was this topic helpful?
Thanks for your feedback.
The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

Content types
Landing pages
Everything you need to manage and administer content within Brightspot CMS.

Admin configurations
A guide for installing, supporting and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
A guide for configuring different integrations to support a multitude of use cases.

Google Analytics
Apple News