Getting Started
Request access, create a key, import the published contract, and send your first Partner API request.
Getting Started
Use this path to go from access request to a first successful Partner API call with the published contract and the correct security posture.
1. Request approved access
Contact info@nowtoprint.com with:
- company name and website
- integration use case
- expected volume or rollout stage
- whether you need webhook, XJDF, or private-beta partner onboarding
2. Create a sandbox key
After approval, generate a sandbox credential in the partner portal Developer area.
| Environment | Prefix | Base URL |
|---|---|---|
| Sandbox | ntp_test_* | https://api.nowtoprint.com/api/v1 |
| Live | ntp_live_* | https://api.nowtoprint.com/api/v1 |
Use sandbox first. Live credentials are registry/private-beta controls for approved workflows; they do not turn on public GA traffic, RFQ creation, quote automation, order automation, webhooks, or Master Data data-product access by themselves.
3. Import the contract
Start from the published OpenAPI file:
Import that URL into Postman, Bruno, or Insomnia before writing production code. It keeps payloads, examples, and expected responses aligned with the public contract.
4. Send a first request
Use an estimate request to validate auth, payload shape, and environment wiring:
curl -X POST https://api.nowtoprint.com/api/v1/estimate \
-H "Authorization: Bearer ntp_test_your_key" \
-H "Content-Type: application/json" \
-d '{
"category": "flyer",
"quantity": 1000
}'
Once that succeeds, re-check the contract before RFQ work. The current public RFQ create/list
routes are launch-disabled and return 501 until the canonical L5 catalog/RFQ resolver is enabled.
5. Prepare for an approved rollout
Before any approved live workflow:
- rotate away any shared onboarding keys
- store the live key in managed secrets
- implement webhook verification only for webhook-enabled pilots
- log request IDs and honor
Retry-After - test idempotent retry handling on any enabled write operation
- confirm that required routes are present in
/docs/api/openapi.yaml
Next steps
War dieser Artikel hilfreich?
Verwandte Artikel
Last updated on