製品機能

API Access and Integration for Component Intelligence

Pull part lookups, BOM scoring, lifecycle forecasts, and obsolescence alerts from Z2 directly into your ERP, PLM, and risk dashboards through a documented REST API.

概要

API Access and Integration lets you embed Z2's component intelligence into the tools your team already uses instead of asking them to log into one more system. A documented REST API exposes part lookup, BOM submission, score retrieval, and alert webhooks, so lifecycle stage, compliance status, and supplier risk surface inside your ERP, PLM, or internal risk dashboard. You submit a BOM, get every line scored against the same data that drives the platform, and receive a webhook the moment a part draws a PCN or moves toward end-of-life. Risk reaches the engineer at the point of decision, not after a manual export.

Put component risk where your team works

Endpoints for the full workflow

The API covers the path a part takes through your process: look up any of 1B+ components by manufacturer part number, submit a full BOM for batch scoring, retrieve lifecycle, compliance, and supplier risk scores on demand, and register webhooks for alerts. A BOM you push through the submission endpoint returns the same line-level scoring you see in Part Risk Manager, so your internal dashboard reflects obsolescence forecasts, country-of-origin flags, and approved vendor list coverage without a person re-keying anything.

GET /v1/parts/score
MPNLifecycleScore
GRM188R71H104KA93DActive92
TPS54331DRNRND61
EP4CE15F23C8NEnd-of-life34
LM2596S-ADJActive88

Webhooks that push change to you

Alert webhooks turn Z2 from a place you check into a feed that reaches your systems on its own. When a part on a tracked BOM draws a PCN, slips to NRND, or hits a last-time-buy notice, Z2 posts the event to your endpoint so a ticket opens or a dashboard updates with no polling. That matters because roughly 30% of discontinuations ship with no proactive notice from the manufacturer, and a webhook tied to Z2's lifecycle forecasting catches the silent ones your team would otherwise find at the next buy.

POST webhook /events
ADSP-BF512BSWZ-4
Analog Devices / tracked BOM
Mar 04
PCN issued
Mar 04
Webhook delivered 200
Apr 18
Status: NRND
Sep 30
Last-time-buy

Authentication and enterprise scale

Every call authenticates with an API key under role-based access control, so you scope what each integration and team can read and keep BOM data partitioned the way your organization requires. Rate limits are sized for enterprise volume, with dedicated throughput available when you score large BOMs or refresh many programs at once. Complete documentation and ready-to-use code samples mean your engineers wire the first lookup from day one rather than reverse-engineering the contract.

API KEY / RBAC
key_prod_7f3a
Procurement integration scope
Part lookup Allowed
BOM submission Allowed
Score retrieval Allowed
Admin / billing Denied

Part of Part Risk Manager

API Access and Integration is one capability inside Part Risk Manager, Z2's component risk platform. Every endpoint reads from the same data layer that powers lifecycle forecasting, compliance screening, supplier risk, and part-to-site mapping in the interface, so a score you fetch over the API is the score your team sees on screen. That shared foundation keeps your ERP, PLM, and the platform aligned on one version of each part's risk, with no second source to reconcile.

機能

Part Risk Manager

API Access & IntegrationはZ2DataのPart Risk Managerに搭載された機能の一つであり、the industry's largest component intelligence platform. Search and score 1B+ parts across obsolescence, compliance, sourcing, and supplier risk, all in one view.

Part Risk Managerを詳しく見る →

よくあるご質問

What can the API return for a part or BOM?

Endpoints cover part lookup, BOM submission, and score retrieval, returning lifecycle stage, compliance status, supplier risk, and country-of-origin data. The scores match what your team sees inside Part Risk Manager because both read the same data layer.

How do the alert webhooks work?

You register an endpoint, and Z2 posts an event whenever a tracked part draws a PCN, moves to NRND, or hits a last-time-buy notice. This pushes obsolescence and lifecycle changes into your systems without polling.

How is access secured and rate limited?

Each request uses an API key with role-based access control, so you scope what every integration can read. Rate limits are sized for enterprise volume, with dedicated throughput available for large or frequent BOM scoring jobs.

Bring Z2 component risk into the tools you already run.