Channel API

gistfile1.json

{
  schedules : [
    {
      name: 'logogarden',
      content: [
        {
          type: 'imageList',
          images: [
            {
              type: image
              .. custom properties ..
            }
          ]
          .. custom properties ..
        },
        {
          type: 'snippet',
          .. custom properties ..
        }
      ]
    },
    {
      name: 'blog',
      content: [
        {
          type: 'aticle',
          .. custom properties ..
        }
      ]
    }
  ],
  schema: {
    image: {
      ... specification of image type ...
    },
    snippet: {
      ... specification of image type ...
    }
  }
}

Note: Schema is optional, you can request it as part of the API call if desired

I feel like 'channels' makes more sense than 'schedules' or is this gist representing a single channel that has multiple schedules?

channel probably makes more sense to the developer who is consuming the API, but the schedule makes more sense, and is more useful metaphor for content creators. I think that model will make more sense to developers too, in the long run