Recipe Cost Calculator API

Recipe Cost Calculator provides a full-featured RESTful API that lets you read and manage your data programmatically. Use it to integrate RCC with POS systems, ordering platforms, accounting software, or your own custom tools.

We recommend always checking the actual API Documentation to ensure you have the most up-to-date API Specification and endpoints.

API Documentation: https://recipecostcalculator.net/api/index.html

Quick Start

Base URL: https://recipecostcalculator.net/api/v1/

Interactive docs: [recipecostcalculator.net/api](https://recipecostcalculator.net/api) (includes request examples and schemas)

OpenAPI spec: [recipecostcalculator.net/api/openapi.yml](https://recipecostcalculator.net/api/openapi.yml) (machine-readable, OpenAPI 3.0)

Authentication

Two authentication methods are supported. For most integrations, an API key is the simplest option.

API Key

Pass your key in the x-api-key header:

curl https://recipecostcalculator.net/api/v1/recipes \
  -H "x-api-key: YOUR_KEY" 

Generate API keys from your User Settings page. Keys can be scoped as read-only or read/write.

JWT Token

Obtain a token by posting your credentials to /api/auth/login. Tokens are valid for 6 months.

curl -X POST https://recipecostcalculator.net/api/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com", "password": "your_password"}' 

Then pass the token in the Authorization header:

curl https://recipecostcalculator.net/api/v1/recipes \
  -H "Authorization: Bearer YOUR_TOKEN"

Response Format

All responses are JSON. Timestamps use ISO 8601 format. Common HTTP status codes:

  • 200 -- Success

  • 204 -- Success (no content)

  • 401 -- Unauthorized (invalid or missing credentials)

  • 403 -- Forbidden (insufficient permissions, e.g. read-only key on a write endpoint)

  • 404 -- Not found

  • 422 -- Unprocessable entity (validation errors)

API Key Management

You can create and manage API keys from your User Settings page inside Recipe Cost Calculator. Each key can be scoped as:

  • Read-only -- can only access GET endpoints

  • Read/write -- full access to all endpoints

Was this helpful?