Partner API
Commercial API surface for estimates, RFQs, quotes, orders, and partner workflow automation.
Partner API
Master Data external-dark
Master Data data-product APIs are runtime-dark for external partners. The current path is internal pre-live/private-beta only. Partner API does not expose Master Data canonical write authority, private evidence, supplier rates, cost, margin, or payout fields until the future external-productization controls are live.
The Partner API lets approved agencies, platforms, and enterprise buyers create print demand from their own systems and route execution into NowToPrint.
What it is for
Use the Partner API when you need to:
- price print products from your own product or portal
- create RFQs programmatically
- receive supplier quotes and accept the right offer
- place and track orders without leaving your own workflow
- connect downstream systems through signed webhooks
Typical flow
Use POST /api/v1/estimate to validate payload shape and pricing posture before opening a live
RFQ.
Submit POST /api/v1/rfq with product, quantity, artwork, delivery, and commercial context.
Accept the winning quote and continue into order creation and tracking.
Access posture
Partner API access is entitlement-based. It is enabled through approval, rollout state, and for deeper integrations, contract-led onboarding.
| Area | Current posture |
|---|---|
| Authentication | Bearer API keys with ntp_test_* and ntp_live_* prefixes |
| Limits | Governed by entitlement and rollout state |
| Webhooks | Enabled per organisation and event family |
| Production use | Requires approved access and production-ready server-side key handling |
Public resources
Generated API Reference
Fumadocs OpenAPI reference for public Partner API endpoints and schemas.
Getting Started
Request access, create a key, import the spec, and send a first request.
Quickstart
Short hands-on path for your first estimate and RFQ flow.
Authentication
Bearer keys, security practices, permissions, and quota behavior.
Endpoints
High-level endpoint map for estimates, RFQs, quotes, orders, and preflight.
Examples
cURL, Node.js, Python, and webhook verification snippets.
Webhooks
Signed delivery, retry posture, and payload handling guidance.
Canonical contract
The public Partner API contract is published at /docs/api/openapi.yaml.
Treat this file as the machine-readable source of truth for public client generation and contract review.
Internal Master Data, admin-only, dark private-beta and future data-product routes are intentionally
excluded from this public contract.
For rendered endpoint docs, use Partner REST API Reference.
When not to use Partner API
- Use XJDF / PrintTalk when your source system is an MIS or ERP that needs standards-based exchange.
- Use the preflight surface described in OpenAPI Explorer when your main goal is queued PDF analysis rather than quote and order automation.
Next: Getting Started ->
War dieser Artikel hilfreich?
Verwandte Artikel
Zuletzt aktualisiert