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

The Authentication API from Kitchen Stories — 10 operation(s) for authentication.

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

This API exposes 10 operations across 10 paths, and defines 11 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.

10 operations 10 paths 11 schemas 2 GET8 POST

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 Authentication 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 10

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

Authentication 10
POST
/authenticate/deprecated
Authenticate and get a bearer token for the subsequent calls to the api
autenticate body → 200
POST
/authenticate/appleid/
Authenticate using Apple ID, get a bearer token for subsequent calls
autenticate-appleid body → 200
POST
/authenticate/google/
Authenticate using Google Account, get a bearer token for subsequent calls
autenticate-google body → 200
POST
/authenticate/facebook/
Authenticate using Facebook Account, get a bearer token for the subsequent calls
autenticate-facebook body → 200
POST
/authenticate/credentials/
authenticate and get a bearer token for the subsequent calls to the api
autenticate-credentials body → 200
POST
/register/
Create a new user with email and password
register-credentials body → 200
GET
/users/validate/email
validate email link - generated by ultron on account creation (note no trailing slash on this endpoint)
validate-email 2 params → 200
POST
/password/forgot/
Send out a password forgot e-mail if the account exists
password-forgot body → 200
GET
/password/reset/
Reset the user password (needs password forgot payload token)
password-reset 2 params → 200
POST
/installations/
Create a new installation in the database
create-installation body → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are create_installation (17 properties), installation (17 properties), email_registration (6 properties), apple_auth (4 properties). Each schema is shown below with its type and property counts.

email_auth
object
4 properties 2 required
access_token
object
1 property 1 required
user_token
object
2 properties 2 required
email_registration
object
6 properties 4 required
apple_auth
object
4 properties 3 required
google_auth
object
3 properties 2 required
errors
object
1 property 1 required
installation
object
17 properties 1 required
facebook_auth
object
3 properties 2 required
forgot_password
object
1 property 1 required
create_installation
object
17 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kitchenstories-authentication-api-openapi.yml Raw ↑

Other APIs Kitchen Stories publishes across the network.

Kitchen Stories Articles Admin API
Kitchen Stories Articles 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
Kitchen Stories Personalization API
Where this information came from

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