Repair data API
Public content as JSON. API keys are available for higher limits and future additional data.
GET /api/v1/repair-assessment?device=…&issue=…Repair decision: options, cost ranges, savings, recommendation (5 levels), reasoning, risks, confidence, sources, data date. Optional age (years), condition (good|fair|poor), country (DE), lang – or q=free text
GET /api/v1/devicesAll devices with available repairs
GET /api/v1/devices/{deviceId}/repair-optionsRepair options, costs, assessment, sources (optional ?issue=akku-wechseln)
GET /api/v1/search?q=…Rule-based device and symptom search
GET /api/v1/shops?ort=10115&radius=5Repair shops from OpenStreetMap (ODbL)
GET /llms.txtCompact overview for AI assistants
Example
curl "https://www.fixwert.com/api/v1/repair-assessment?device=iphone-13&issue=akku-wechseln&age=4&condition=fair&lang=en"
Decision response fields
deviceId, manufacturer, model, issue, repairOptions, repairCostRange, replacementCostRange (same model new – or used if no longer sold new), estimatedSavings, recommendation, reasoningSummary, riskFactors, confidence, sources, lastUpdated, urls. Website, calculator and API use the same calculation – the answers are identical.
AI assistants and MCP
The endpoints are designed to serve directly as tools of an MCP server (e.g. find_device → /api/v1/search, assess_repair → /api/v1/repair-assessment). Our own MCP server is prepared but not yet published; until then please use the JSON API.
Terms of use
- Without a key: 60 requests per minute per IP. With a key (header x-api-key): 600 per minute.
- Credit “Fixwert” with a link to the respective page (field url).
- Costs are estimated ranges with verification status – not offers, no guarantee.
- Repair-shop data comes from OpenStreetMap and is licensed under the ODbL.