Integrations

What exists today: a generic REST/webhook API

Suprocure exposes a REST API secured with a per-company API key (organizations.erp_api_key, verified server-side with the service role — never exposed to the browser). This endpoint exposes orders/products/requests as JSON views; requests raised in your ERP can be mapped through this API into Suprocure.

Supplier matching is keyed by tax number, product matching by material code (upsert) — a repeated tax number/material code updates the existing record instead of duplicating it.

• Per-company API key, verified server-side with the service role
• Order/product/request REST views
• Tax-number-keyed supplier upsert, material-code-keyed product upsert

SAP, Logo, Netsis, Dynamics — scope clarity

Suprocure does NOT have a named, certified "native connector" for these four systems — that claim is deliberately not made. These systems are listed as example ERPs commonly connected through the generic REST/webhook API above, by your integration team or an iPaaS tool. Before onboarding, we recommend confirming exact scope (which fields, which direction, what frequency) with our team.

Webhooks (push notifications) — to be verified

Whether an order approved in Suprocure pushes back to your ERP via an instant webhook is a scope item that cannot be fully verified from this repository; confirm with our team before onboarding.