How do the Collections Feeds work?

A feed is a container of content that can be queried through our API.

We export our feeds in two different formats: JSON and ATOM. 

Below is the schema for the JSON and the ATOM feeds. 

*Italicized items are optional fields (an article may or may not have this field).

  • num_found: Number of articles within collection
  • collection_item_set: Contains each collection item
    • collection_item: Individual content item
      • images: List of image attributes
        • guid: Unique image identifier
        • description: Description of image
        • caption: Caption associated with image
        • attribution_text: Attributes creative credit to image's licensor and/or creator
        • urls: Image's URL 
      • description: Article’s content within HTML tags
      • title: Article’s title
      • topic_set: List of article’s tagged topics
      • author_set: Article’s author
      • source:
        • name: Content Provider’s name (ex. New York Times)
        • country: Country article was published in
      • published_at: Date/time article was originally published
      • link: Unique identifier for content in provider feed; often a link to original/canonical article's URL. It is helpful to include this for SEO. If no canonical link is provide, this will be the same as the guid for the article.
      • guid: Unique article identifier
      • thumbnail: Information regarding content’s featured image
        • original_image: Original thumbnail identifier
        • guid: Image’s unique identifier
        • link: Link to image url
      • custom fields: A number of fields which can contain further information about the article.
        • custom_fields_set: This is a container of custom field key/value pairs
    • position: Order within the feed
    • guid: Feed element identifier
    • type: Description of post (ie: article, blog post)​​
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk