Quickstart

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.

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_partner_v2_<issued-key-id>_<secret>"

---

2. Check the estimate boundary

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. Create an RFQ

curl -i -X POST https://api.nowtoprint.com/api/v1/rfq \
  -H "Authorization: Bearer $NOWTOPRINT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "catalogProductUid": "ntp:book:a5:softcover:books",
    "title": "Quickstart book request",
    "category": "book",
    "quantity": 1000,
    "deliveryCity": "Istanbul"
  }'

The estimate boundary still returns 503 PARTNER_ESTIMATE_CAPABILITY_UNAVAILABLE. A valid RFQ returns 201 with an RFQ id and tracking code. Handle 422 PARTNER_RFQ_INVALID, 429 PARTNER_RFQ_QUOTA_EXCEEDED, and 503 PARTNER_RFQ_CATALOG_CONTEXT_UNAVAILABLE explicitly. category is the buyer-selected Marketplace group; the server verifies it against the L2 product resolved from catalogProductUid and does not invent either value.

---

4. Re-check the published contract before automation

RFQ detail and owned-RFQ quote reads are live in the Partner v1 contract. Move into quote acceptance, order, or webhook automation only after those operations are present in the published contract 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 ->

Replace the sample product ID with a published product in your environment. RFQ retry identity comes from its body; retries consume minute quota, while the same body reuses the daily reservation.