RECY Systems API

RECY Systems is a specialized ERP for the metal-recycling and scrap industry. This page is an independent design exercise that asks what a well-designed RECY Systems API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.

By Alex Klarfeld•July 8, 2026

This page is an independent analysis by Supergood of what a well-designed RECY Systems API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing RECY Systems product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.

What is RECY Systems?

RECY Systems is a specialized ERP for the metal-recycling and scrap industry. Acquired by AMCS in 2019, it now operates as the AMCS Platform for Metal and powers ferrous and non-ferrous metal recyclers, plus operators handling paper, wood, plastics, and textiles, from inbound material receipt through grading, trading, logistics, and settlement. Recyclers use RECY to run inventory and stock control, grade incoming material, trade and broker commodities, integrate weighbridges and platform scales, manage inbound and outbound freight, process purchase and sales orders, administer contracts and pricing, and reconcile cash and cashless payments through the AMCS Financials accounting module.

Core product areas include:

Inventory and stock control for ferrous, non-ferrous, and mixed-material yards
Material grading, including a mobile grading app for yardmasters to grade material during unloading with contamination monitoring
Commodity trading and brokerage used by large recycling trading companies
Weighbridge and truck/platform scale integration for reliable data flow with no duplicate entry
Transport and logistics with intelligent dispatching and freight cost control across inbound and outbound flows
Purchase and sales orders with self-billing, plus contract management for volume, metal content, fixed/unfixed pricing, and recovery percentages
Pricing management for frequent market-driven adjustments, cash and cashless purchasing, and AMCS Financials for AR/AP, automated accounting entries, and country-specific VAT compliance

An API for a platform like this would naturally organize around its core data entities:

Stock items, material grades, inventory lots, locations
Grading records, contamination assessments, yard tickets
Purchase orders, sales orders, contracts, brokerage trades
Weighbridge tickets, gross/tare/net weights, scale readings
Suppliers, customers, transport orders, freight records
Cash/cashless payments, self-billing invoices, settlements, accounting entries

The RECY Systems Integration Challenge

Recyclers run their entire yard on RECY daily, but the operating data, stock, grades, trades, weights, logistics, and payments, stays trapped inside an enterprise platform with no public self-serve API:

No public developer portal: RECY/AMCS Platform for Metal is sold as an enterprise system, with access gated behind partnership and implementation agreements rather than a self-serve API key
Vertical, yard-specific data model: grades, recovery percentages, weighbridge tickets, and metal-content contracts don't map to any generic ERP schema
Mobile-captured grading: material grading happens in a mobile app at the point of unloading, so that data lives behind app sessions rather than an open endpoint
Scale and weighbridge coupling: weights flow directly from truck and platform scales into RECY, and any integration must respect that hardware-driven data path
Country-specific financials: self-billing, VAT compliance, and AMCS Financials accounting rules vary by jurisdiction and must be preserved on every transaction
Volatile pricing: frequent market-driven price changes mean trades, contracts, and settlements carry effective-dated pricing that integrations have to handle precisely

What a RECY Systems API Could Look Like

If RECY Systems exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:

First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
Consistent resources: normalized JSON schemas and pagination across the platform's core objects
Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
Entitlement awareness: endpoints scoped to what each customer's licensing actually permits

The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.

How AI agents could connect to software like RECY Systems: MCP servers for software without a public API →

Need This Kind of Access Today?

If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.

Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model.
Scope the Integration
We design the access pattern around your workflows and entitlements.
Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.

RECY Systems on the API Report Card

Potential API Endpoints

Authentication

POST/authenticate

Would authenticate to a RECY Systems / AMCS Platform for Metal deployment with username/password or MFA and obtain a session token for downstream calls.

Inventory

GET/stock

Would list inventory and stock items by material grade, location, and lot, with on-hand quantities and movements.

Grading

POST/create_grading

Would submit a material grading record, grade, weight, and contamination assessment, captured at the point of unloading.

Orders

GET/purchase_orders

Would retrieve purchase and sales orders with supplier/customer, contract, pricing, and self-billing details.

Orders

POST/create_purchase_order

Would create a purchase or sales order against a contract with material, quantity, and effective-dated pricing.

Weighbridge

GET/weigh_tickets

Would pull weighbridge tickets with gross, tare, and net weights and the originating truck or platform scale reading.

Payments

GET/payments

Would list cash and cashless payments, self-billing invoices, and settlements posted through AMCS Financials.

Use Cases

Sync stock and grading data into your warehouse

- Pull inventory, stock movements, and material grades from RECY into a central data warehouse - Stream mobile-captured grading and contamination records to quality and reporting tools - Reconcile on-hand stock by grade and location across multiple yards

Automate trading, contracts, and pricing

- Push purchase and sales orders against contracts with metal content, recovery percentage, and effective-dated pricing - Surface brokerage trades and contract positions to trading and risk dashboards - Update prices in bulk as the market moves without manual portal entry

Reconcile weights, logistics, and freight

- Sync weighbridge tickets and gross/tare/net weights into downstream systems with no duplicate entry - Match inbound and outbound transport orders to freight cost records - Feed dispatch and logistics data to planning and customer-notification workflows

Close the loop on payments and financials

- Sync cash and cashless payments and self-billing invoices into AR/AP - Reconcile settlements and automated accounting entries from AMCS Financials into your general ledger - Preserve country-specific VAT handling on every transaction

Connect via No-Code Tools

Automate this platform from the no-code stack you already use.

Zapier

Wire a portal Zapier can't reach natively into your zaps.

Read the guide →

Make

Slot a no-API portal into your Make scenarios as one more module.

Read the guide →

n8n

Add a no-API portal as an n8n node like any other.

Read the guide →

Technical Requirements

Authentication

Would require username/password and MFA with managed session handling

Connectivity

Would build on authenticated browser and application flows over the RECY / AMCS Platform for Metal deployment

Response format

Normalized JSON across stock, grading, orders, weighbridge, and payment objects

Rate limits

Adaptive throttling tuned to your deployment to avoid platform-side limits

Session management

Would need automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for stock, grading, and weigh tickets with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for grading, weighbridge tickets, order changes, and payment postings

Latency

Design target: sub-second reads on cached entities; multi-second writes when posting orders and financial transactions

Throughput

Design target: horizontally scaled workers sized to multi-yard volume across high-frequency weighing and grading

Reliability

Retry, backoff, and idempotency keys for orders, settlements, and accounting entries

Versioning

Clear versioning and change management would matter as RECY Systems evolves

Frequently asked questions

Yes. Material grading captured in the mobile grading app at the point of unloading is exposed through the same normalized API surface, alongside stock, weighbridge, and order data.

Yes. Cash and cashless payments, self-billing invoices, settlements, and automated accounting entries, including country-specific VAT handling, are available through the API for reconciliation into AR/AP and your general ledger.

Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.

The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.

No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual RECY Systems product or service.

Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.

Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.