One versioned REST API, three audiences. The same endpoints that power the BoardBid web app are available for you to integrate into ERPs, e-commerce platforms, procurement tools, or custom workflows. HTTP/JSON, Bearer auth, sub-second response times.
curl -X POST https://boardbid.io/api/v1/parse-quote \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "RSC 15x10x5 32ECT 871 qty for QEP"}'
{
"api_version": "1.0.0",
"request_id": "req_lxyz123_abc",
"parse": {
"type": "RSC",
"length": 15, "width": 10, "depth": 5,
"ect": 32, "quantity": 871, "customer": "QEP"
},
"confidence": 0.98,
"trace": { "latency_ms": 823, "model": "claude-sonnet-4-5" }
}
URL-path versioning (`/v1/`). Stable schema. Breaking changes require a new major version with a 12-month deprecation window. No surprise API changes.
Every request returns a `request_id` in the response header and body. Trace object includes latency, token counts, and model version. File a support issue with one ID and we have the full context.
The parser runs the same way for every call — no silent fast-paths. Regex validator double-checks high-precision fields. Confidence scores are calibrated and reliable.
Our architecture decisions are documented publicly. Know why we chose Claude-always over regex-first, why we log every parse, why we version the way we do. No black box.
Bearer tokens. Rotatable. Scoped keys for different environments. RLS-based tenant isolation. Nothing exotic, nothing to learn — auth works the way every other REST API does.
Supabase Edge Functions, SOC 2 Type II. Global distribution. The infrastructure under you is battle-tested so you can focus on what you're building.
Hook up an inbox, watch for quote requests, parse incoming emails, populate your CRM. Your sales team stops retyping customer emails.
A buyer picks "custom box" on your Shopify store. Dimensions flow to BoardBid, pricing returns in sub-second, add-to-cart happens inline.
NetSuite, SAP, Odoo — wherever your pricing lives, BoardBid slots in as the quote-intake layer. Structured data in, priced quote out.
Your sales rep pastes a customer message into Slack, the bot parses it and replies with a priced quote before the customer finishes their coffee.
Full API reference, authentication guide, and code examples at /docs. Free tier includes 500 parse calls per month.
Read the docs →