Most receipt OCR APIs return fixed fields — you get what they give you. ReceiptAPI lets you define your own output schema. Need just vendor + total? Pass that. Need line items with SKUs and unit costs? Define exactly that. ✦ Send a receipt image (URL, upload, or base64), pass a schema, get back clean JSON ✦ 100 free receipts/month — at $9/mo for 1,000 receipts, a fraction of what competitors charge ✦ Async endpoint for batch processing ✦ Simple REST API with API key auth

Tines — The intelligent workflow platform

The intelligent workflow platform

Hey Product Hunt! 👋 I built ReceiptAPI after spending way too long writing custom parsers for receipt data in my own projects. Every solution I found either locked me into a rigid schema or cost a fortune at scale. The custom output schema feature is what I'm most excited about — instead of getting a wall of fields you didn't ask for, you tell the API exactly what you need and that's all you get back. It makes downstream processing much cleaner. A few things I'd love feedback on: - Is the schema format intuitive? (docs at receiptapi.dev/documentation#custom-schema) - What use cases are you building for — expenses, accounting, inventory? - Any fields or features missing for your workflow? Free tier is 100 receipts/month, no credit card needed. Would love for you to try it and tell me what breaks. 🙏

Tines — The intelligent workflow platform

The intelligent workflow platform

ReceiptAPI

Extract exactly the JSON fields you need from any receipt

Extract exactly the JSON fields you need from any receipt