oanor
Sign up free
Marketplace Pricing Features Sign in

API · /dough-api

Dough Calculator API

healthy 3,002 Subscribers

Pizza and bread dough maths as an API, built on baker's percentages — where the flour is always 100% and every other ingredient is expressed as a percentage of the flour weight. The dough endpoint computes a full recipe in grams (flour, water, salt, yeast, oil and sugar) from a target quantity — either a number of dough balls and a ball weight, a total dough weight, or a flour weight — together with a hydration and salt/yeast percentages, or a built-in style preset (Neapolitan, New York, Detroit, Sicilian, focaccia, ciabatta, baguette, sandwich). The hydration endpoint converts between flour, water and hydration percentage and classifies the dough from stiff to extremely wet. The presets endpoint returns the common dough styles as baker's percentages with typical ball weights. Everything is computed locally and deterministically, so it is instant and private. The yeast figure is instant dry yeast (use roughly three times as much fresh). Ideal for recipe and baking apps, pizzeria and bakery tools, meal-planning and kitchen-scale integrations, and food blogs. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is dough formulation by baker's percentage; for ingredient volume-to-weight and oven-temperature conversion use a cooking API.

#dough #pizza #bread #baking #recipe #developer-tools
api.oanor.com/dough-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/dough-api/openapi.json
/api/dough-api/llms.txt

Discovery: GET /api/index.json lists every API.

Dough Calculator API — live data on the oanor API marketplace

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
79 ms
Server probes · 24h
Subscribers
3,002
active
Total calls
76
last 7 days
status Full status page → · 12 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 10,435 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 10,435 calls/month
  • 2 req/sec
  • Dough + hydration + presets
  • No credit card
Sign in to subscribe

Starter

€11.95 /month

  • 20,050 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 20.05k calls/month
  • 8 req/sec
  • 8 style presets
  • Email support
Sign in to subscribe

Pro

€31.85 /month

  • 250,500 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 250.5k calls/month
  • 20 req/sec
  • Recipe / baking pipelines
  • Priority support
Sign in to subscribe

Mega

€69.85 /month

  • 1,295,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 1.295M calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Tezos (XTZ) On-Chain API — oanor API marketplace

Tezos (XTZ) On-Chain API

Live on-chain data from the Tezos blockchain (XTZ), a self-amending liquid-proof-of-stake Layer 1, served from the public TzKT indexer API — no key, nothing cached. The account endpoint returns any address's state: its XTZ balance, account type, the baker it delegates to, its staked balance, transaction count and first-activity date. The tokens endpoint returns the FA1.2 and FA2 token balances an address holds, with the token contract, symbol and decoded amount. The operations endpoint returns the account's most recent transactions with the counterparty, amount, status and time. The network endpoint returns the live chain state: the head block level, the current cycle, the active protocol and the total XTZ supply. Everything is read live from TzKT, nothing stored. This is the Tezos on-chain layer for any wallet, explorer, baking, NFT or analytics app. Distinct from the XRP Ledger, Stellar, TRON, Aptos, Algorand, EVM and Solana on-chain APIs and from price feeds — this is Tezos account state, delegation, token balances, operations and ledger health. 4 endpoints, no key on our side.

api.oanor.com/tezos-api

 Baking Pan Scaler API — oanor API marketplace

Baking Pan Scaler API

Baking-pan maths as an API, computed locally and deterministically — the area and scale-factor numbers a baker resizes a recipe between pans with. The trick everyone gets wrong is that a recipe scales by the pan’s AREA, not its diameter, so a 10-inch round holds far more batter than a 9-inch. The area endpoint gives the surface area of any pan — round and springform as π/4·d², square as s², rectangle as length × width, and bundt or tube pans as the ring (the outer circle minus the centre hole) — so a 9-inch round is 63.6 in², an 8-inch square 64 and a 9×13 is 117; add a depth and it returns the volume in cubic inches and cups. The convert endpoint gives the scale factor to move a recipe from one pan to another, factor = target area ÷ source area: a 9-inch round to a 9×13 is ×1.84, and two 8-inch rounds really do equal one 9×13. Pass an ingredient amount and it scales it for you, with a note to keep the batter depth similar and adjust the bake time. Everything is computed locally and deterministically, so it is instant and private. Ideal for baking, recipe, meal-prep and kitchen app developers, recipe-scaling and substitution tools, and culinary software. Pure local computation — no key, no third-party service, instant. Inches. Live, nothing stored. 2 compute endpoints. For ingredient unit conversion use a cooking API.

api.oanor.com/panscale-api

 Candy Temperature API — oanor API marketplace

Candy Temperature API

Candy-making maths as an API, computed locally and deterministically — the sugar-syrup stage numbers a confectioner reads a thermometer by. As sugar syrup boils it passes through named stages, each a temperature window with its own texture and uses, and getting within a few degrees is the difference between fudge and toffee. The stage endpoint names the stage for a temperature: 238 °F is the soft-ball stage (fudge, fondant, pralines), 305 °F is hard-crack (toffee, brittle, lollipops), and it handles °F or °C and the off-the-chart cases — still a thin syrup below thread, or darkening to burnt past caramel. The range endpoint gives the temperature window and uses of a named stage, from thread (223–234 °F) through soft-ball, firm-ball, hard-ball, soft-crack and hard-crack to caramel (320–350 °F), in both °F and °C. The altitude endpoint applies the rule that matters in the mountains: cook to 1 °F lower for every 500 feet of elevation, since water boils cooler, so a 300 °F hard-crack recipe is done at 290 °F at 5,000 feet. Everything is computed locally and deterministically, so it is instant and private. Ideal for baking, confectionery, recipe and kitchen app developers, candy-thermometer and timer tools, and cooking-class software. Pure local computation — no key, no third-party service, instant. Use a calibrated thermometer. Live, nothing stored. 3 compute endpoints.

api.oanor.com/candytemp-api

 Jam & Preserve API — oanor API marketplace

Jam & Preserve API

Jam and preserve maths as an API, computed locally and deterministically — the sugar, setting-point and yield numbers a jam maker, preserver or recipe app works a batch to. The sugar endpoint sets the sugar from the sugar-to-fruit ratio: a traditional full-sugar jam is 1:1, so 1 kg of fruit takes 1 kg of sugar for a 2 kg batch at 50 % sugar, while lower ratios (0.6–0.75) make a softer, fresher, less-sweet preserve that needs added pectin and keeps less well — the sugar both preserves and helps the gel. The setting-point endpoint gives the gel temperature adjusted for altitude: jam sets at about 4.5 °C (8 °F) above the temperature water boils at — 104.5 °C at sea level — but because water boils lower as you climb (roughly 1 °C per 285 m), the target falls to near 99 °C at 1500 m, so cooking to the sea-level figure up a mountain over-boils the batch. The yield endpoint boils the batch down to a target soluble-solids (Brix): jam keeps at about 65 % Brix, the finished weight = the solids (sugar plus the fruit's own ~10 % dry matter) ÷ the target Brix, and the rest evaporates as water — 1 kg sugar and 1 kg fruit boils down to about 1690 g of jam, losing roughly 310 g of water. Everything is computed locally and deterministically, so it is instant and private. Ideal for preserving and recipe tools, homestead and kitchen apps, and food-production calculators. Pure local computation — no key, no third-party service, instant. Gel chemistry, not canning safety. 3 compute endpoints. For processing-time altitude adjustment use a canning API.

api.oanor.com/jam-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Dough Calculator API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Dough Calculator API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Dough Calculator API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Dough Calculator API cost?
Dough Calculator API has a free tier with 100 calls / month. Paid plans start at €11.95 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Dough Calculator API GDPR-compliant?
All requests to Dough Calculator API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/dough-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/dough-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/dough-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/dough-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.