Endpoints
High-level endpoint map for Partner API estimate, RFQ, quote, order, and preflight flows.
Endpoints
This page provides a human-readable map of the main Partner API routes. The machine-readable source
of truth remains /docs/api/openapi.yaml.
Base URL
https://api.nowtoprint.com/api/v1
Estimate
| Method | Path | Purpose |
|---|---|---|
POST | /api/v1/estimate | Get a pricing signal before opening a live RFQ |
RFQs and quotes
| Method | Path | Purpose |
|---|---|---|
POST | /api/v1/rfq | Create a new RFQ |
GET | /api/v1/rfq | List RFQs for the current organisation |
GET | /api/v1/rfq/{id} | Retrieve RFQ status and current summary |
GET | /api/v1/rfq/{id}/quotes | List supplier quotes for the RFQ |
POST | /api/v1/rfq/{id}/accept | Accept the selected quote and continue the flow |
Orders
| Method | Path | Purpose |
|---|---|---|
GET | /api/v1/orders | List orders for the current organisation |
GET | /api/v1/orders/{id} | Retrieve order status and details |
Preflight from Partner API
| Method | Path | Purpose |
|---|---|---|
POST | /api/v1/preflight | Submit a file for commercial-side preflight analysis |
Use the dedicated preflight contract from /docs/api/preflight-openapi.yaml
when you need the queued v3 validation surface directly.
Master Data
Master Data is internal-only for public Partner API users. External data-product APIs, partner onboarding, quotas, SLAs, certification controls and commercial contracts remain a future maturity track and are not part of the public Partner API surface.
Master Data external-dark
Do not treat Master Data contract IDs as live public endpoints. They stay runtime-dark for external partners until route exposure, authorization, audit, rate-limit storage, onboarding, and legal controls are live. Public/partner routes cannot write canonical L2 truth and must return sanitized projections without private payload fields.
Write-operation guidance
- use bearer auth for every request
- send
Idempotency-Keyon metered reads or writes that may be retried;X-Idempotency-Keyremains accepted for older clients - trust response headers for entitlement-aware limit behavior
- prefer webhooks for asynchronous state changes instead of aggressive polling
Related docs
War dieser Artikel hilfreich?
Verwandte Artikel
Zuletzt aktualisiert