Quickstart
Fast path to a live Partner RFQ and fail-closed capability checks.
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. 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" \
-H "Idempotency-Key: quickstart-rfq-001" \
-d '{
"catalogProductUid": "ntp:book:a5:softcover:books",
"title": "Quickstart flyer order",
"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 ->
هل كانت هذه المقالة مفيدة؟
مقالات ذات صلة
Last updated on