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 QA API

The QA API from Kitchen Stories — 4 operation(s) for qa.

Kitchen Stories QA 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 QA. 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 6 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 6 schemas 1 DELETE2 POST1 PUT

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 QA 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 — 1 DELETE, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

QA 4
PUT
/qa/users/me/
Update currently authenticated user
qa-user-update body → 200403
DELETE
/qa/users/me/{pk}/
Delete a given User
qa-user-me-delete 1 param → 200404
POST
/qa/ugc/recipe/{pk}/accept/
Accept / Approve given UGC recipe
qa-ugc-accept 1 param body → 200404
POST
/qa/ugc/recipe/{pk}/reject/
Reject given UGC recipe
qa-ugc-reject 1 param → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are user (19 properties), qa_user_update_json (8 properties), image (6 properties), qa_ugc_recipe_accept (4 properties). Each schema is shown below with its type and property counts.

image
object
6 properties 1 required
form_response
object
1 property 1 required
qa_ugc_recipe_accept
object
4 properties
qa_user_update_json
object
8 properties
qa_user_public_update_image
object
2 properties
user
object
19 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kitchenstories-qa-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
Where this information came from

This is an independent, third-party profile of Kitchen Stories QA 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.