GET /health
Example: /health
Success: API status such as {"status":"ok"}.
Developer surface
Use Convematik's no-auth JSON endpoints for single conversions, batch conversions, catalog discovery, unit metadata and lightweight widgets. Error responses use HTTP 400 with JSON shaped as {"error":"..."}.
Single conversions use query parameters and return JSON.
GET https://api.convematik.com/convert?value=1&from=kg&to=lb
{
"value": 1.0,
"from": "kg",
"to": "lb",
"result": 2.20462262185
}
Batch output appears here after the API responds.
<iframe title="Convematik converter" src="https://convematik.com/widget/?value=78&from=kg&to=lb" width="360" height="420" loading="lazy"></iframe>
Open the widget gallery for preset embeds and attribution snippets.
All endpoints return JSON. Use https://api.convematik.com in production or http://localhost:8000 for local API development.
GET /healthExample: /health
Success: API status such as {"status":"ok"}.
GET /capabilitiesExample: /capabilities
Success: version, tool count, endpoint list and feature states.
GET /toolsExample: /tools
Success: generated tool catalog grouped by category.
GET /searchExample: /search?q=kg
Success: up to 20 matching tool records.
GET /convertExample: /convert?value=78&from=kg&to=lb
Success: numeric result with original value and unit aliases.
POST /batchExample: JSON body with conversions array.
Success: ordered result list for up to 100 conversions.
GET /romanExample: /roman?roman=XIV or /roman?integer=2026
Success: Roman numeral and integer pair.
GET /fractionExample: /fraction?numerator=42&denominator=56&op=simplify
Success: simplified fraction, decimal or percent result.
GET /tableExample: /table?from=kg&to=lb&start=1&end=10&step=1
Success: conversion table rows.
GET /bmiExample: /bmi?weight=70&height=1.75&unit=metric
Success: BMI value and category.
GET /electricalExample: /electrical?watts=1200&volts=120&target=amps
Success: calculated watts, amps or volts.
GET /percentageExample: /percentage?mode=percent-of&x=20&y=150
Success: percentage result and formula.
GET /ageExample: /age?birth_date=1990-01-15&as_of=2026-06-12
Success: years, months, days and total days.
GET /date-differenceExample: /date-difference?start=2026-06-01&end=2026-06-12
Success: day difference with inclusive flag.
GET /tipExample: /tip?subtotal=80&tip_percent=20&people=2
Success: tip, total and per-person split.
GET /discountExample: /discount?price=120&discount_percent=25&tax_percent=8
Success: discount, discounted price, tax and total.
GET /fuel-costExample: /fuel-cost?distance=240&efficiency=30&fuel_price=3.75
Success: fuel used and trip fuel cost.
GET /unit-priceExample: /unit-price?price=12.99&quantity=3&unit=lb
Success: price per unit.
GET /unitsExample: /units
Success: unit aliases grouped by category for selectors and widgets.
GET /openapi.jsonExample: /openapi.json
Success: OpenAPI 3.0 contract for client generation and docs.
Use the public API when your app needs structured JSON, the iframe widget when a reader needs a visible converter inside another site, and focused static pages when the goal is search traffic, user education and shareable formulas. All three surfaces should start from the same source-of-truth conversion engine rather than separate hard-coded factors.
tool-pages.json, unit-catalog.json and openapi.json for discovery and integration planning.Validate one conversion manually before automating it, handle HTTP 400 JSON errors, preserve the original input alongside the result, and avoid sending sensitive payloads to API endpoints that are not designed for private text processing. For front-end embeds, include attribution and link users back to the full converter when they need another unit pair.