Помощь NowToPrint
Помощь NowToPrint
Центр помощи
Getting Started
Platform Overview
Marketplace
Print Shop
Prepress
Design Studio
Orders & Delivery
Notifications
Free Tools
Templates
VDP (Variable Data Printing)
Developer & API
API Reference
OpenAPI Explorer & Spec Reference
Getting StartedAuthenticationEndpointsWebhooksExamplesPartner API Access ModelQuickstart
Webhook Access & DeliveryXJDF API RehberiXJDF Master Data Model
FAQ
Technical Reference
Admin Panel
Developer & APIPartner api
  1. Developer
  2. Partner API
  3. Endpoints

Endpoints

High-level endpoint map for Partner API estimate, launch-disabled RFQ, and excluded future surfaces.

Разработчикdocs2 мин чтенияПроверено 13 июн. 2026 г.

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

MethodPathPurpose
POST/api/v1/estimateGet a pricing signal before opening a future RFQ flow

RFQs

MethodPathPurpose
POST/api/v1/rfqLaunch-disabled; authenticates, checks permission, then returns 501
GET/api/v1/rfqLaunch-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

MethodPathPurpose
POST/api/v1/preflightSubmit 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-Key on metered reads or writes that may be retried; X-Idempotency-Key remains accepted for older clients
  • trust response headers for entitlement-aware limit behavior
  • prefer webhooks for asynchronous state changes instead of aggressive polling

Related docs

Authentication

Quickstart

Examples

Webhooks

Была ли эта статья полезной?

Похожие статьи

  • IAM Guide
  • Organisation Management
  • Registration, Onboarding, and Activation Operations
  • Roles & Permissions Reference
Edit on GitHub

Последнее обновление

Authentication

Bearer-key authentication, entitlement-aware limits, and secure key handling for the Partner API.

Webhooks

Signed webhook delivery for Partner API quote, order, and workflow events.

На этой странице

EndpointsBase URLEstimateRFQsQuote and order flowPreflight from Partner APIMaster DataWrite-operation guidanceRelated docs
Ask AI Assistant