A content object typically represents either an article or an element that belongs to an article. Being images, movies, related articles, fact boxes, and so on. All related elements are embedded to save you from having to request each object separately. Each content type can be recognized by the model attribute in the response object. A separate endpoint, giving an overview of all the different models will be provided soon.
A related content object (found in _embedded/relations) can either be inline or not. If inline the object is meant to be embedded into either the leadText or body of the object. Relations that are not inlined should be presented alongside the content, depending on design and use cases.
An inlined relation will have an inlineid set. This id will match the id of an amedia-embed tag in one of those fields. The client must either implement support for replacing the amedia-embed tags with proper content found in the relation or strip the tag away.
Hopefully the response format and attribute names should be pretty self-explaining, but we do recognize that we need some more detailed documentation. This, and examples, will be added soon.
GET/content/{contentId}
Produces a content presentation
application/json; charset=UTF-8; type=content
Description: ACPID, a unique ID for the document within ACP