Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kitchen Stories Personalization API

The Personalization API from Kitchen Stories — 8 operation(s) for personalization.

Kitchen Stories Personalization 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 Personalization. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 13 operations across 8 paths, and defines 18 schemas. It is described by OpenAPI 3.0.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.

13 operations 8 paths 18 schemas 1 DELETE8 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.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 Personalization 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 13

Across 8 paths, the API surfaces 13 operations — 1 DELETE, 8 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Personalization 13
GET
/personalization/
Get personalization flags for user (or preferences set)
personalization-get 1 param → 200
POST
/personalization/
Obtain a preferences set (for logged out preferences usage)
personalization-post body → 200
PUT
/personalization/
Update personalization flags for user (or preferences set)
personalization-put 1 param body → 200404
GET
/personalization/preferences/
Get a list of personalization preferences
personalizationpreferences-get 1 param → 200404
POST
/personalization/preferences/
Insert a new personalization preference
personalizationpreferences-post 1 param body → 200403
GET
/personalization/preferences/{uuid}/
Get a single personalization preference by uuid
personalizationpreferences-get-by-uuid 2 params → 200404
PUT
/personalization/preferences/{uuid}/
Update a single preference
personalizationpreferences-put-by-uuid 2 params body → 200404
DELETE
/personalization/preferences/{uuid}/
Delete a single preference
personalizationpreferences-delete-by-uuid 2 params → 200404
GET
/personalization/options/
Get a list of available personalization options (and their values)
personalizationoptions-get 1 param → 200
GET
/personalization/options/{uuid}/
Get a single option information by its uuid
personalizationoptions-get-by-uuid 1 param → 200404
GET
/personalization/options/{uuid}/values/
Get available values for a given option uuid
personalizationoptions-values-get 1 param → 200404
GET
/personalization/options/{option-uuid}/values/{value-uuid}/
Get a single value for an option by its uuid
personalizationoptions-values-get-by-uuid 2 params → 200404
GET
/personalization/feed/
Get the personalized feed for the current user
personalization-feed-get 3 params → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are user_public (13 properties), personalization_option (9 properties), personalization_option_value (8 properties), image (6 properties). Each schema is shown below with its type and property counts.

personalization
object
4 properties
image
object
6 properties 1 required
links
object
4 properties 2 required
personalization_preference_body
object
2 properties 2 required
tag
object
5 properties
meta
object
1 property 1 required
form_response
object
1 property 1 required
personalization_option_paginated
object
3 properties 3 required
personalization_preference
object
5 properties 2 required
personalized_feed_collection
object
2 properties 2 required
personalization_body
object
4 properties
personalization_option
object
9 properties 3 required
user_public
object
13 properties 4 required
personalization_option_value_paginated
object
3 properties 3 required
personalization_preference_paginated
object
3 properties 3 required
personalization_option_value
object
8 properties 1 required
personalization-feed
object
1 property 1 required
personalized_feed_recipe
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kitchenstories-personalization-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 Content Collections API
Kitchen Stories Feed API
Kitchen Stories Indexer API
Kitchen Stories Ingredients API
Kitchen Stories Other API
Kitchen Stories Personalization Admin API