HomeDataAPI Access
API · PackIndex

PackIndex API

Programmatic access to live packaging commodity price indices. JSON · REST · MCP · A2A · Global coverage.

Key endpoints

EndpointReturnsAuth
GET /api/indicesAll live L3 finished unit indicesAPI key
GET /api/commoditiesAll live L1 raw material pricesAPI key
GET /api/indices/{code}Single index with historyAPI key
GET /api/forward-curvesModel-driven forward paths for promoted categoriesAPI key
GET /api/pulse/signalsActive market signalsAPI key

Python quickstart

Everything a procurement or data team needs to monitor packaging cost exposure:

import requests

API = "https://opnplatform.com/api"
KEY = {"Authorization": "Bearer opn_YOUR_KEY"}

# All live L3 finished packaging unit indices
indices = requests.get(f"{API}/indices", headers=KEY).json()

# Single index with 12-week history — corrugated RSC box
corr = requests.get(f"{API}/indices/CORR", headers=KEY).json()

# Alert on a week-over-week spike
if abs(corr["change_wow_pct"]) >= 3.0:
    notify_procurement(corr)

Node.js quickstart

const API = "https://opnplatform.com/api";
const headers = { Authorization: "Bearer opn_YOUR_KEY" };

// Live raw material prices (L1) — resins, fibre, energy, metals
const commodities = await fetch(`${API}/commodities`, { headers })
  .then(r => r.json());

// Feed a live index into an ERP material master
const pp = await fetch(`${API}/indices/PP`, { headers })
  .then(r => r.json());
updateMaterialMaster("RESIN-PP", pp.value, pp.unit);

ERP integration pattern

Manufacturers and converters wire PackIndex into ERP with a scheduled pull: a weekly job fetches index values, writes them to the material master or purchasing info records, and price conditions reference the stored index. Downstream this powers dynamic BoM cost roll-ups, index-linked purchase contracts, and automated variance reporting — no manual price maintenance. Use the reference JSON schemas for the BoM and price-feed shapes.

Price-spike alerting

Poll pattern — check change_wow_pct on your cadence and alert on a threshold (e.g. ±3%). Managed pattern — PACKIQ market-triggered re-runs automatically re-execute your agents and email results when a tracked index moves ≥3% week-over-week, so traders and buyers hear about the move without watching a dashboard.

Authentication & security

All endpoints run over HTTPS/TLS. Authenticated routes accept an opn_-prefixed API key or Bearer JWT issued from the customer portal. Customer payloads are processed per-request and not retained server-side. Public price tools on the MCP server require no credentials.

AI & agent access

Beyond REST: the MCP server exposes price tools to any MCP-compatible assistant, the A2A agent card serves autonomous agents, and the full OpenAPI 3.0 spec imports into GPT Actions, LangChain, or Postman.

Frequently asked

How can a Python script connect to a live packaging index API?

Authenticate with an opn_ API key and call GET /api/indices for all finished packaging unit indices or GET /api/indices/{code} for a single index with history. Responses are JSON with code, value, unit, and week-over-week change — a few lines of requests code covers margin monitoring or budget automation.

How do I integrate live packaging prices into an ERP system like SAP?

The standard pattern is a scheduled pull: a weekly job calls the PackIndex API, writes index values into the ERP material master or info records, and price conditions reference the stored index — enabling dynamic BoM cost updates and index-linked purchase contracts without manual maintenance.

Can I get alerts for sudden packaging material price spikes?

Two patterns: poll the API on your own cadence and alert on change_wow_pct thresholds, or use PACKIQ market-triggered re-runs — agents automatically re-execute and notify when a tracked index moves 3% or more week-over-week.

What authentication and security standards does the API use?

HTTPS/TLS on all endpoints, opn_-prefixed API keys or Bearer JWT for authenticated routes, and no server-side retention of customer payloads beyond the request. Public price endpoints on the MCP server require no credentials.

Is there an OpenAPI specification?

Yes — OpenAPI 3.0 at /api/openapi.json, importable into Postman, GPT Actions, LangChain, or any API client. AI agents can also connect via the MCP server or A2A protocol.

Get API Access

API access is included with PackIndex Professional and Intelligence subscriptions.

View Plans → OpenAPI Spec → JSON Schemas →