MiseOS API Documentation

The MiseOS API provides programmatic access to the MiseOS kitchen management platform.

It allows applications to manage users, kitchen stations, menus, ingredients, and internal kitchen workflows used in professional kitchens.

Most endpoints follow REST principles and return JSON responses.
Real-time features are delivered through WebSocket and Server-Sent Events (SSE).

Base URL

#

Current version of the API is available at:

https://miseos.corral.dk/api/v1

All endpoints listed in this documentation are relative to this base URL.

Versioning

#

The MiseOS API uses URL versioning.

Current version:

https://miseos.corral.dk/api/v1

Future breaking changes will be released under /api/v2.

Resources

#

The following sections describe the available API resources and their endpoints.

• Authentication
• Users
• Allergens
• Stations
• Dish Suggestions
• Dishes
• Weekly Menus
• Ingredient Requests
• Shopping Lists
• Notifications
• Menu Inspirations
• Takeaway Offers
• Takeaway Orders

Authentication

#

Most endpoints require authentication via a JWT token in the Authorization header. Tokens are obtained through the login endpoint.

Examples of public endpoints include:

• POST /auth/register
• POST /auth/login
• GET /weekly-menus/current
• GET /weekly-menus/by-week

Authorization: Bearer <token>

JWT tokens expire after 30 minutes.

You can obtain a token by calling the login endpoint.

Quick Start

#

1. Register a user

POST /auth/register

2. Login

POST /auth/login

3. Use the returned token

Authorization: Bearer

Example request to get user profile:

curl -H "Authorization: Bearer <token>" \
https://miseos.corral.dk/api/v1/users/me

Roles

#

Error Format

#

All errors follow this format:

{
  "statusCode": 404,
  "message": "User with ID 99 was not found.",
  "timestamp": "2026-03-27 12:00",
  "path": "/api/v1/users/99",
  "referenceId": "abc123xyz"
}

Error Fields

#

Common Error Status Codes

#