Developer Hub
Technical resources for integrating NowToPrint with public API guides, webhook delivery, XJDF workflows, and machine-readable specs.
The current RFQ create and organization-owned RFQ/quote read contract is generated at /api/v1/marketplace/openapi.json. The older /docs/api/openapi.yaml publication is a separate reference; do not assume the documents are identical. Confirm the environment origin and approved capabilities during onboarding.
This is the public developer surface for NowToPrint. Use it to evaluate the platform, import the canonical specs, and choose the right integration path before production rollout.
Public vs internal docs
Public developer docs cover onboarding, authentication, webhook delivery, XJDF interoperability, and published API contracts. Internal setup notes and engineering runbooks stay outside this surface.
Quickstart Path
Request access
Contact info@nowtoprint.com with your company, integration goal, and expected volume.
Obtain an approved credential
Obtain a one-time Credential V2 secret through authorized operator issuance after approval. The dashboard does not currently generate keys.
Import the spec
Pull the published OpenAPI files from /docs/api/* into Postman, Bruno, Insomnia, or your SDK
pipeline.
Check the fail-closed boundary
Start with POST /api/v1/estimate; valid auth reaches a capability-specific RFC 9457 503, not
a price estimate.
Turn on async delivery
Add signed webhooks before production so quote and order state changes reach your systems.
Integration Surfaces
| Surface | Authentication | Best for |
|---|---|---|
| Partner API | Credential V2 bearer | Live RFQ create/read plus disabled estimate/order checks |
| XJDF / PrintTalk | Public metadata; costing/session and XJMF sender auth are separate | MIS, ERP, and standards-based workflow interoperability |
| Webhooks | Signed delivery | Event-driven order, quote, and fulfillment orchestration |
| Published specs | Public download | Client generation, contract review, and QA tooling |
| LLM discovery corpus | Public text endpoints | AI retrieval, GEO, and machine-readable indexing |
Key Concepts
| Concept | What to know |
|---|---|
| Key families | The V2 prefix does not select an environment |
| Access model | API access is entitlement-based, not a generic self-serve pricing toggle |
| Idempotency | RFQ deduplication uses its parsed body; check each other route separately |
| Contract source of truth | Use the generated RFQ contract plus allowlisted reference publications |
| Async operations | Webhooks and queued workflows should be treated as first-class paths |
| Governance | Confirm registry/rollout state; use returned reset metadata for quota |
Reference Docs
Partner API
Commercial integration surface for live RFQ create/read and disabled estimate/order boundaries.
Getting Started
Access request, key creation, sandbox posture, and first API request.
Authentication
Bearer keys, permission posture, quota behavior, and secure key handling.
Webhook Access & Delivery
Signed delivery, retry posture, and entitlement-aware access guidance.
XJDF Integration
CIP4 XJDF 2.2, PrintTalk 2.2, and XJMF-aligned interoperability.
OpenAPI Explorer
Published spec downloads, Swagger preview, and surface-by-surface contract guidance.
Published Resources
Partner REST API Spec
Older allowlisted reference; use the generated Marketplace RFQ contract for current RFQ operations.
XJDF / PrintTalk Spec
Machine-readable XJDF, PrintTalk, and XJMF-aligned contract.
Preflight Engine Spec
Queued PDF inspection contract for the preflight surface.
Swagger Preview
Interactive browser preview for the published XJDF and PrintTalk spec.
Common Integration Patterns
White-label commerce
Use the Partner API to create/read governed RFQs and validate capability-specific fail-closed handling while estimate and order application adapters remain disabled.
Workflow interoperability
Use XJDF and PrintTalk when your source system is an MIS, ERP, or print workflow platform that needs standards-based message exchange.
Event-driven orchestration
Use signed webhooks to trigger CRM updates, customer communication, fulfillment, and internal workflow transitions.
Contract-first delivery
Import the specs before writing production code so QA, SDK generation, and partner onboarding all start from the same contract.
Error Handling Quick Reference
| HTTP code | Meaning | Recommended action |
|---|---|---|
400 | Invalid request payload | Compare your request with the published schema |
401 | Missing or invalid credentials | Verify bearer key, header formatting, and environment |
403 | Organization capability denial; wrong credential scope can be 401 | Request the missing capability or broader access |
404 | Unknown resource or route | Recheck IDs, route family, and API surface version |
429 | Limit or rollout ceiling | Use returned reset metadata; honor Retry-After when present |
5xx | Platform or dependency failure | Retry with backoff and keep request identifiers |
Full error taxonomy: Error Codes
Was this article helpful?