Supplier Data API

Supplier-authorized data for DPP systems Redy does not host.

The Supplier Data API service lets suppliers package reusable evidence, authorize access, and deliver versioned DPP-ready records into manufacturer workflows or external platforms.

View service contract API examples

Supplier data contract

request -> package -> grant -> deliver

Grant-based

Data owner

Supplier

Suppliers maintain reusable records and decide who can consume each package.

Consumer

Any DPP stack

Manufacturers, PLM/PIM systems, LCA tools, and external DPP platforms can consume authorized packages.

Delivery

API + export

Pull package JSON, export evidence bundles, and subscribe to package-state changes.

Access

Revocable

Grant state, expiry, revocation, freshness, and audit entries travel with the data.

Service contract

The API boundary starts with supplier authorization.

Redy can broker supplier evidence for systems outside the Redy host because the data object carries request context, package version, access terms, and delivery evidence.

Request

A buyer asks for specific fields and evidence needed for a DPP use case.

Supplier orgProduct scopeRequested fieldsUse case

Package

The supplier turns source material into a reusable, scoped evidence package.

Structured valuesSource documentsAttestationVersion

Grant

Access is authorized for a buyer, platform, or integration client.

ConsumerScopeExpiryRevocation state

Delivery

The authorized package moves into the consuming DPP workflow.

API responseExport bundleWebhook eventAudit ref

API consumers

Supplier data should move without forcing a host migration.

Manufacturer DPP teams

Request missing supplier fields and subscribe to updates when evidence changes after publication.

External DPP platforms

Consume supplier-authorized packages without replacing the primary DPP hosting platform.

PLM, PIM, ERP, and LCA systems

Pull evidence values, document references, and freshness metadata into existing product-data workflows.

Examples and events

The service is concrete enough for integration planning.

The deeper API page keeps endpoint examples and event details. This service page shows the buyer-facing contract.

Sample request

Ask for supplier evidence by scope

POST /api/v1/supplier-evidence/requests
Authorization: Bearer buyer_api_key

{
  "supplierOrgId": "sup_7f4",
  "productRef": "BATTERY-MODULE-24",
  "requiredFields": [
    "recycledContent",
    "materialComposition",
    "dueDiligenceEvidence"
  ],
  "requestedUse": "battery_dpp_readiness"
}

supplier_evidence.package.updatedsupplier_evidence.grant.revokedsupplier_evidence.package.expiringsupplier_evidence.trust_state.changed

Supplier control is explicit

The API service is built around supplier grants, not hidden buyer-side scraping or unrestricted marketplace access.

Evidence is packaged, not dumped

Each response needs scope, source context, provenance, review state, freshness, and version metadata.

Integrations stay lane-bound

Supplier-platform keys, buyer keys, webhook consumers, and exports should carry distinct scopes and audit trails.

Need endpoint-level examples?

The existing Supplier Evidence API page keeps the request, package, export, and webhook examples for technical review.

Open API examples Backup service