The Apollo Apps Content API allows you to access the content synchronized form the different sources that you have plugged in your sections.

The Content API is built on a REST architecture. On each source, it's possible to call different methods, each meeting a specific need.  

The Content API requests are secured and can be called only from the app itself (or by a plugin in the app). To facilitate your tests, you can use an API Console in your backend.

The auth management in the Content API is handled automatically by the request method of the Apollo Apps Plugin API.

1. General structure of Content API requests

The Content API calls URLs always follow this structure:

http://[myapp].http://Myapp.apollochurchapps.com
.com/apps/[endpoint]/[section_id]/[arguments...]

You can find the list of available sources for your app in your Apollo Apps backend.

The detailed list of endpoints is described in this article : Endpoints List.

2. General structure of Content API responses

The responses of the Content API are always formatted as a JSON dictionary, and follow a general structure.

The responses contain an array of items resulting of the request, and several other informations.

The structure of the Content API responses is detailed in this article : Return structures & values.

3. Item type and inherited types

The data returned by the Content API is always formatted as JSON dictionaries respecting the Item format.

Each entry (article, video, tweet, photo, event, etc.) is an Item, having several additional keys specific to its type.

The Item format specifications and the additional keys for each type are described in this article : Items types documentation

Did this answer your question?