TraceLink
TraceLink, Inc. is a Massachusetts-based supply chain digitalization company for the life sciences and healthcare industries, best known for pharmaceutical serialization and track-and-trace compliance (US DSCSA, EU FMD, and roughly two dozen national regimes) delivered on its multienterprise OPUS network platform. TraceLink exposes several distinct integration surfaces rather than one REST API: a set of publicly served SOAP/WSDL services on api.tracelink.com (Serialized Operations Manager, Product Track, Serial Number Exchange), a synchronous REST API for Smart Event Manager, an event-driven OPUS Platform API where every call is a POST to a single /api/events endpoint carrying a header/payload envelope keyed by a fully qualified eventName, a GraphQL endpoint at /api/graphql used by the Agile Process Teams app, and asynchronous B2B message exchange over AS2, SFTP, and HTTP POST using EPCIS, EDI ANSI X12, SAP IDoc, and TraceLink XML canonical documents. Its published API guides, canonical JSON Schemas, and code samples are the machine-readable surface catalogued here.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles TraceLink the way a machine reads it — 49 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TraceLink scores 51.3/100 (developing), with a separate agent-readiness read of 42/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from TraceLink's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tracelink/"
title="TraceLink on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tracelink.svg"
alt="TraceLink Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/tracelink/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tracelink/"
title="TraceLink on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tracelink/card.svg"
alt="TraceLink Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile TraceLink
Each block below is one kind of artifact we hold for TraceLink. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
TraceLink Serialized Operations Manager (SOAP)
SOAP web service for serialized operations: commissioning, aggregation, decommissioning, shipment and receipt orders, serial number verification, lot status, market release, sam...
TraceLink Product Track (SOAP)
SOAP web service supporting Product Track pick-and-ship operations for US DSCSA serialized product movement. The WSDL is served publicly from the production API host and declare...
TraceLink Serial Number Exchange (SOAP)
SOAP web service for requesting serial numbers from TraceLink Serial Number Exchange, used by packaging lines and contract manufacturers to obtain serial number ranges. The WSDL...
TraceLink Smart Event Manager REST API
Synchronous JSON/REST API that acts as an event ledger for serial number observations across pharmacy, warehouse, and supply chain activities. Supports Set Event, Get Event, and...
TraceLink OPUS Platform Event API
The OPUS Platform exposes one /api/events endpoint per environment. Every operation is a POST to that endpoint carrying a JSON envelope of header (headerVersion, eventName, owne...
TraceLink OPUS GraphQL API
GraphQL endpoint used by the Agile Process Teams app, exposing genericActionCall and genericGetObject fields that dispatch on an action name and a JSON payload. Introspection is...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
tracelink-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Tracelink Event Surface
ASYNCAPIJSON Schema 37
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Acknowledgment Response
JSON SCHEMAProcessing Acknowledgment
JSON SCHEMAReport Sales Shipment
JSON SCHEMAReport Sales Shipment
JSON SCHEMASerialized Shipment Notice
JSON SCHEMAAdvance Ship Notice
JSON SCHEMAAdvance Ship Notice
JSON SCHEMABatch Master
JSON SCHEMACredit Debit Adjustment
JSON SCHEMAForecast Plan Response
JSON SCHEMAForecast Plan
JSON SCHEMAForecast Plan
JSON SCHEMAInventory Balance
JSON SCHEMAInventory Balance
JSON SCHEMAInventory Update
JSON SCHEMAInventory Update
JSON SCHEMAInvoice
JSON SCHEMAInvoice
JSON SCHEMAInvoice
JSON SCHEMAPayment Remittance
JSON SCHEMAPayment Remittance
JSON SCHEMAPrice Sales Catalog
JSON SCHEMAPrice Sales Catalog
JSON SCHEMAcanonical Product Activity
JSON SCHEMAPurchase Order Acknowledgement
JSON SCHEMAPurchase Order
JSON SCHEMAPurchase Order
JSON SCHEMAReturn Authorization
JSON SCHEMASerialized Shipment Notice
JSON SCHEMAWarehouse Ship Advice
JSON SCHEMAWarehouse Ship Advice
JSON SCHEMAWarehouse Ship Order
JSON SCHEMAWarehouse Stock Transfer Receipt Advice
JSON SCHEMAWarehouse Stock Transfer Receipt Advice
JSON SCHEMAWarehouse Stock Transfer Receipt Advice
JSON SCHEMAWarehouse Stock Transfer Ship Advice
JSON SCHEMAWarehouse Stock Transfer Ship Advice
JSON SCHEMAScroll within the panel for all 37 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Tracelink Trust Center
ISO/IEC 27001:2022, ISO/IEC 27017:2015, ISO 9001:2015, SOC 2 Type II, ISAE 3000 Type II, CyberVadis
SECURITYResources
Every other property we hold for TraceLink — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tracelink · machine-readable index on apis.io
This is an independent, third-party profile of TraceLink, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.