How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kitchen Stories Content Collections API

The Content Collections API from Kitchen Stories — 4 operation(s) for content collections.

Kitchen Stories Content Collections API is one of 37 APIs that Kitchen Stories publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content Collections. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 46 schemas. It is described by OpenAPI 3.2.0, at version 3.

Requests are made against 3 base URLs: https://api.kitchenstories.io/api, https://api.dev.kitchenstories.io/api, http://localhost:8000/api.

4 operations 4 paths 46 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3
Base URL
https://api.kitchenstories.io/api
Authentication
HTTP Bearer, API Key
License
Resource Areas
1

Authentication & Security 2

Kitchen Stories Content Collections API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as X-Ultron-User (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Content Collections 4
GET
/content-collections/
List available content collections
content-collection-get-list → 200
GET
/content-collections/{uuid}/
Get a single content collection
content-collection-get-detail 1 param → 200404
GET
/content-collections/{uuid}/items/
List available content collection items for a given collection
content-collection-item-get-list 1 param → 200
GET
/content-collections/{collection-uuid}/items/{item-uuid}/
List a single content collection item
content-collection-item-get-detail 2 params → 200

Schemas 46

The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are recipe (24 properties), article (16 properties), video (15 properties), user_public (13 properties). Each schema is shown below with its type and property counts.

feed_article
object
4 properties 2 required
image
object
6 properties 1 required
content_collection_items_pagination
object
3 properties 3 required
content_collection_item
object
4 properties 2 required
publishing
object
4 properties 3 required
article_text
object
2 properties 2 required
article_simplified
object
11 properties 11 required
child_item
object
5 properties 3 required
article_quote
object
2 properties 2 required
legacy_unit
object
3 properties 1 required
category_simplified
object
5 properties 3 required
article_headline
object
2 properties 2 required
user_public
object
13 properties 4 required
meta
object
1 property 1 required
size
object
4 properties 1 required
additional_information
object
2 properties 2 required
content_meta_carousel
object
3 properties 2 required
path_item
object
3 properties 3 required
comment_image
object
5 properties 5 required
article_recipes
object
2 properties 2 required
article_video
object
2 properties 2 required
video
object
15 properties 6 required
recipe_ingredient
object
9 properties 1 required
recipe
object
24 properties 12 required
recipe_simplified
object
13 properties 9 required
content_meta_external_link
object
1 property 1 required
content_meta
object
5 properties 3 required
content_meta_external_product
object
5 properties 3 required
article_proscons
object
2 properties 2 required
content_meta_markdown
object
1 property 1 required
content_meta_faq
object
2 properties 2 required
article
object
16 properties 13 required
content_collections_pagination
object
3 properties 3 required
tag
object
5 properties
article_image_gallery
object
2 properties 2 required
content_collection_detail
object
4 properties 2 required
recipe_utensil
object
6 properties 1 required
links
object
4 properties 2 required
article_shopping_tips
object
2 properties 2 required
characteristic
object
2 properties 2 required
feed_recipe
object
4 properties 2 required
unit
object
5 properties 4 required
wagtail_meta
object
3 properties 1 required
article_cta_button
object
2 properties 2 required
step
object
7 properties 1 required
content_collection
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kitchenstories-content-collections-api-openapi.yml Raw ↑

Other APIs Kitchen Stories publishes across the network.

Kitchen Stories Articles Admin API
Kitchen Stories Articles API
Kitchen Stories Authentication API
Kitchen Stories Categories Admin API
Kitchen Stories Categories API
Kitchen Stories Content Collections Admin API
Kitchen Stories Feed API
Kitchen Stories Indexer API
Kitchen Stories Ingredients API
Kitchen Stories Other API
Kitchen Stories Personalization Admin API
Kitchen Stories Personalization API
Where this information came from

This is an independent, third-party profile of Kitchen Stories Content Collections API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.