What can the Rechain API read and write?
Almost everything your team keeps in Rechain. The API has 159 operations, and 106 of them write. Seasons and product costings are read-only.
| Area | What the API covers | Access |
|---|---|---|
| Products | Products, with bulk create, update and archive; product categories; custom product fields | Read and write |
| Colorways | Colorways, their fields and values, size identifiers | Read and write |
| Images | Product photos, colorway photos and sketches, from a file, an image URL or base64 | Read and write |
| Materials | Components such as fabrics, trims and packaging, linked to products and colorways; colors; BOM templates | Read and write |
| Fit and construction | Measurement templates, points of measure, construction details | Read and write |
| Development | Development stages, reviews and sample requests, sample measurements, trackers, attachments | Read and write |
| Production | Quality control inspections, purchase orders, suppliers | Read and write |
| Planning | Seasons, product costings | Read only |
Should you use the API or a built-in integration?
If we already connect to the system you use, start with that built-in integration. Your team won't have to build it or keep it running. Rechain connects to Shopify, NetSuite, ApparelMagic, Madden Analytics, Adobe Illustrator, Canva, Retraced and Carbonfact. See all integrations, or how the ERP integrations and Shopify integration work.
The API is for everything else. With it, your developers can:
- Connect a system we don't have an integration for. Send purchase orders, products and suppliers to an ERP or warehouse system, and read them back.
- Load your catalog when you move to Rechain. Create your products and import their photos from image URLs instead of typing them in.
- Report on development. Pull products, sample reviews, quality inspections and costings into your BI tool or a spreadsheet.
- Update records from your own tools. Move a product to its next development stage or update a tracker when something changes in another system.
How does API access work?
You get a token from Workspace Settings > Integrations > API, and every request sends it as an Authorization: Bearer header to https://api.rechain.co/public/v1/. The limit is 100 requests per account per minute. If you go over, the API returns a 429 error with a Retry-After header. Every response also shows how much of the limit you've used, in an X-Rechain-Api-Call-Limit header. Loading a big catalog? Use the bulk product endpoints.
Plenty of PLM vendors say they have an open API and stop there. We publish ours: the full reference and an OpenAPI 3.1 spec are in the Rechain API docs, so your developers can check every endpoint before you sign. The API Access add-on costs $250 a month on top of your plan. See pricing.
Does Rechain have an MCP server?
Yes. Rechain's MCP server lets an AI assistant like Claude or ChatGPT work in your Rechain account. It covers the same ground as the API, so you can ask the assistant to look up or update your products, components and suppliers.
To connect, add https://api.rechain.co/public/v1/mcp as an MCP server or connector in your AI assistant, then sign in with your Rechain account. You don't need an API token. The assistant can only see and change what your Rechain permissions already allow. The MCP server comes with your Rechain subscription, so you don't need the API Access add-on to use it.

