The Retraced Public API lets your own systems, such as your ERP or PLM, exchange data with Retraced automatically. For example, you can keep your products, bills of materials, orders and audits in sync without uploading files by hand. This article explains what you can do with the API, how to create an API key and where your developers find the technical documentation.
Want to ask questions about your data in plain language instead of building an integration? See Retraced MCP: connect your AI assistant to your Retraced data.
What you can do with the API
The API covers these areas:
Products: Create and update your styles, variants and SKUs.
Bills of materials and materials: Add the components and material composition of your products.
Orders (Beta): Create and update orders and order lines.
Audits: Read and manage audits, their reports and corrective action plans.
CAPA: Read and manage audit findings, corrective and preventive actions and plans.
Files: Upload files to Retraced.
Partner integrations: Connect a digital product passport (DPP) or label provider, or a life cycle assessment (LCA) provider.
Create an API key
The API is an additional feature. Retraced switches it on for your company. If you don’t see the API Keys tab in your company settings, ask your Retraced account admin.
Every request to the API needs an API key. To create one:
Click your company name in the top-right corner, then Company settings.
Open the API Keys tab. It lists the keys your company already has, with their label and creation date.
Click + Add API Key in the top-right corner of the table.
In Create API Key, enter a Label, for example the name of the system that will use the key, so you can tell your keys apart later. Then click Create.
Your new key appears under API Key. Click the copy icon next to it, store the key somewhere safe, then click Done.
The key is shown only once. Copy it before you click Done, because you can’t retrieve it later. If you lose it, create a new one.
The key belongs to your company. Everything done with it only reaches your own company’s data. Treat it like a password and share it only with the people who build your integration.
Delete an API key
If you no longer need a key, or it may have been shared with the wrong people, click the bin icon in the Actions column of the API Keys tab. Any system that still uses the key can no longer connect to Retraced, so give it a new key first if it should keep working.
Before you start building
Test before you go live: The API works with your live Retraced data. If you need a safe place to build and test your integration, contact your Customer Success Manager.
Use your own codes: You don’t need to look up Retraced IDs first. You can use your own IDs for the records you create, and your suppliers’ Internal Company Code to identify them.
Your systems check for changes: Retraced doesn’t notify your systems when data changes. Your integration requests the latest data on a regular schedule, for example once a day.
Build on version 2: Older API versions (v0 and v1) are only kept for existing integrations.
Documentation for your developers
Share the Integration Guides with the people who build your integration. They’ll find everything there: a Getting Started guide, one guide per area, the API Reference and the Release Notes.
If you have questions about your integration, contact your Customer Success Manager or [email protected].