Introduction
Enqufy platforms share one core idea: you give the system a document or a workflow, and it returns structured, audit-ready output. Whether that is a freight RFQ, an inventory spreadsheet or a GST return, the building blocks are the same.
Core concepts
- Document AI — upload a file and the engine reads columns, intent and language, returning structured data with confidence scores.
- Matching — records are reconciled under tolerances you control, and anything ambiguous is flagged for a human.
- Delivery — proposals, PDFs and exports carry your brand, with every action logged for audit.
New here? Start with the Quick start for your platform, then read Core concepts to understand how Document AI and matching fit together.
Authenticate a request
All API calls use a bearer token scoped to your company workspace. Pass it in the Authorization header:
# Estimate a freight rate
curl https://api.enqufy.com/v1/rates/estimate \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "origin": "SHA", "destination": "RTM", "container": "40HC" }'
A successful response returns an estimate with a confidence band and recent comparable shipments. See the REST reference for the full schema.
Enqu