What you can do
Every entry runs the identical pinned-Version pipeline, so the same inputs produce the same Receipt regardless of surface — hosted, embedded, or headless.
For the full endpoint reference with request and response schemas, see the API reference.
Core resources
- Quote Intent — the persisted request: inputs, idempotency key, source, and a status of
created | requires_input | processing | succeeded | failed | expired. - Quote Receipt — the immutable outcome evidence.
succeededcarries the full computation (line items, total in integer minor units, payment terms, conditions, derivation) and the pinned Book Version;requires_inputcarries structured missing-input paths and never an amount;failedcarries a machine-readable failure code. - Book Version — the compiled, checksummed artifact a Quote pins. Republishing never rewrites an issued Receipt.
The integration path
- Publish — a Book version to the Environment you want to quote against.
- Authenticate — create a Test API key in the Console Developers section.
- Quote —
POST /v1/quoteswith anidempotencyKey. - Handle outcomes — render
succeeded, collectrequires_input, routefailed. - Distribute — share the hosted quote link, embed the components, or stay headless.
- Go Live — publish to the Live Environment and use a Live key when the Live key lifecycle opens.
Where to start
- New to the API? Start with the Quickstart.
- Need to understand credentials? Read Authentication.
- Want the zero-code launch? See Hosted quote path.
- Want drop-in UI? See Components and embeds.
- Need the full endpoint schema? See the API reference.
Base URL
All API requests are sent to your Kordless instance base URL under/v1/. The exact base URL depends on your deployment.
What the API is not
- The API is not a CRM or a booking system. Quotes end at the Receipt; downstream handoff is yours.
- The API does not expose Book authoring or publication internals beyond the member routes the portal itself uses.
- The API does not expose billing or plan management.