Endpoints
High-level endpoint map for Partner API estimate, launch-disabled RFQ, and excluded future surfaces.
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 future RFQ flow |
RFQs
| Method | Path | Purpose |
|---|---|---|
POST | /api/v1/rfq | Launch-disabled; authenticates, checks permission, then returns 501 |
GET | /api/v1/rfq | Launch-disabled; authenticates, checks permission, then returns 501 |
Quote and order flow
Quote acceptance and order endpoints are not part of the public Partner OpenAPI contract. Treat any
route not listed in /docs/api/openapi.yaml as unavailable for public
client generation until the contract publishes it.
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
Was this article helpful?
Related articles
Last updated