Skip to main content
NowToPrint Help
NowToPrint Help
Help Center
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. Quickstart

Quickstart

Fast path to your first estimate and RFQ launch-disabled check with the Partner API.

Developerdocs2 min readReviewed Jun 18, 2026

Quickstart

If you already have approved access and a sandbox key, this is the fastest path to a working Partner API smoke check.


1. Export your sandbox key

export NOWTOPRINT_API_KEY="ntp_test_your_key"

2. Request an estimate

curl -X POST https://api.nowtoprint.com/api/v1/estimate \
  -H "Authorization: Bearer $NOWTOPRINT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "flyer",
    "quantity": 1000
  }'

3. Check RFQ launch posture

curl -i -X POST https://api.nowtoprint.com/api/v1/rfq \
  -H "Authorization: Bearer $NOWTOPRINT_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: quickstart-rfq-001" \
  -d '{
    "title": "Quickstart flyer order",
    "category": "flyer",
    "quantity": 1000,
    "deliveryCity": "Istanbul"
  }'

The current public contract returns 501 for RFQ create/list until the canonical L5 catalog/RFQ resolver is enabled. Build clients to handle that response explicitly instead of assuming a live RFQ ID is returned.


4. Re-check the published contract before automation

Only move into RFQ detail, quote, order, or webhook automation after those operations are present in /docs/api/openapi.yaml for your environment and your registry entitlement explicitly enables them.


5. Keep webhook work rollout-gated

Signed webhook handling is required for approved event-delivery pilots, but quote/order webhook delivery is not a public-current production enablement. Treat webhook setup as private-beta until your contract, key registry scopes, and rollout state confirm it.


Next: Authentication ->

Was this article helpful?

Related articles

  • IAM Guide
  • Operational configuration security
  • Organisation Management
  • Registration, Onboarding, and Activation Operations
Edit on GitHub

Last updated on

Partner API Access Model

How Partner API access is enabled through package entitlements, rollout state, key registry controls, and contract onboarding.

Webhook Access & Delivery

How webhook access works under the current entitlement model and what delivery guarantees to expect.

On this page

Quickstart1. Export your sandbox key2. Request an estimate3. Check RFQ launch posture4. Re-check the published contract before automation5. Keep webhook work rollout-gated
Ask AI Assistant