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.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.
10 operations10 paths11 schemas2 GET8 POST
Metadata
The identity and technical contract details declared by the specification.
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
autenticatebody→ 200
POST
/authenticate/appleid/
Authenticate using Apple ID, get a bearer token for subsequent calls
autenticate-appleidbody→ 200
POST
/authenticate/google/
Authenticate using Google Account, get a bearer token for subsequent calls
autenticate-googlebody→ 200
POST
/authenticate/facebook/
Authenticate using Facebook Account, get a bearer token for the subsequent calls
autenticate-facebookbody→ 200
POST
/authenticate/credentials/
authenticate and get a bearer token for the subsequent calls to the api
autenticate-credentialsbody→ 200
POST
/register/
Create a new user with email and password
register-credentialsbody→ 200
GET
/users/validate/email
validate email link - generated by ultron on account creation (note no trailing slash on this endpoint)
validate-email2 params→ 200
POST
/password/forgot/
Send out a password forgot e-mail if the account exists
password-forgotbody→ 200
GET
/password/reset/
Reset the user password (needs password forgot payload token)
password-reset2 params→ 200
POST
/installations/
Create a new installation in the database
create-installationbody→ 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), email_auth (4 properties). Each schema is shown below with its type and property counts.
access_token
object
1 property1 required
apple_auth
object
4 properties3 required
email_auth
object
4 properties2 required
user_token
object
2 properties2 required
errors
object
1 property1 required
facebook_auth
object
3 properties2 required
installation
object
17 properties1 required
forgot_password
object
1 property1 required
google_auth
object
3 properties2 required
create_installation
object
17 properties1 required
email_registration
object
6 properties4 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
