Partner API

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.

Master Data external-dark

Master Data data-product APIs are runtime-dark for external partners. The current path is internal pre-live/private-beta only. Partner API does not expose Master Data canonical write authority, private evidence, supplier rates, cost, margin, or payout fields until the future external-productization controls are live. This is a dry-run first, public-safe boundary with no public-current RFQ, quote, order, or webhook claim for Master Data data products before external GA approval.

Partner RFQ create, owned-RFQ read, and owned-RFQ quote read are live. Estimate, quote acceptance, order, and batch-order capabilities remain fail-closed launch boundaries. Authentication, authorization, quota, catalog, and canonical RFQ validation still apply before any write.

What it is for

Use the Partner API when you need to:

create an RFQ against an explicit published catalog product and Marketplace category group
read one RFQ owned by your organization and its supplier quotes
validate authentication, permissions, quota, and fail-closed integration handling
prepare for estimate and order adapters while those capabilities remain disabled with 503
connect downstream systems through signed webhooks

Typical flow

Authenticate

Send a bearer request to a published route and handle 401, 403, and authentication-authority 503 problem details.

Create RFQ

Send catalogProductUid, category, title, quantity, and delivery city. A ready, authorized product reaches the canonical RFQ pipeline; unavailable catalog context returns 503 PARTNER_RFQ_CATALOG_CONTEXT_UNAVAILABLE without reserving the daily RFQ allowance; credential request quota is still consumed.

Future quote/order flow

Estimate and order adapters remain disabled boundaries; they do not return pricing or order records until canonical adapters exist.

Access posture

Partner API access is entitlement-based. It is enabled through approval, rollout state, and for deeper integrations, contract-led onboarding.

Area	Current posture
Authentication	Credential V2 bearer keys with the `ntp_partner_v2_*` prefix
Limits	Governed by entitlement and rollout state
Webhooks	Enabled per organisation and event family
Production use	Requires approved access and production-ready server-side key handling

Public resources

Getting Started

Request access, create a key, import the spec, and send a first request.

Quickstart

Short hands-on path for a live RFQ plus fail-closed estimate handling.

Authentication

Bearer keys, security practices, permissions, and disabled-capability behavior.

Endpoints

High-level endpoint map for live RFQ, disabled estimate/order, and future surfaces.

Examples

cURL, Node.js and route-specific webhook verification guidance.

Webhooks

Signed delivery, retry posture, and payload handling guidance.

Canonical contract

The active RFQ contract is generated at /api/v1/marketplace/openapi.json. The older /docs/api/openapi.yaml remains an allowlisted static reference; reconcile differences before client generation. Internal Master Data, admin-only, dark private-beta and future data-product routes are intentionally excluded from this public contract.

When not to use Partner API

Use XJDF / PrintTalk when your source system is an MIS or ERP that needs standards-based exchange.
Use the preflight surface described in OpenAPI Explorer when your main goal is queued PDF analysis rather than quote and order automation.

Next: Getting Started ->