Parties
Registry endpoints for the third parties referenced by your data and your compliance submissions — today, suppliers; future surfaces (operators, authorising representatives) will slot in under the same prefix.
▶Suppliers
Suppliers are the parties supplying the commodities you place on the EU market. The supplier registry is global: one row per distinct supplier identity across the platform, deduplicated by a fingerprint computed from the identity fields. Per-organization references are tracked through a separate link table so two organizations that source from the same physical supplier point at the same global row but keep their own caller-side identifiers.
See Suppliers for the conceptual overview, including how supplier data is auto-written at ingestion time from upload columns.
▶Endpoints
| Method | Path | Purpose |
|---|---|---|
| GET | /parties/suppliers | List the suppliers your organization has linked |
| POST | /parties/suppliers | Create or reuse a supplier; link to your organization |
| GET | /parties/suppliers/:id | Fetch one supplier |
| PATCH | /parties/suppliers/:id | Edit identity fields on the registry row |
| DELETE | /parties/suppliers/:id | Soft-delete; rejected when any pending DDS references it |
▶Visibility
A supplier is visible to your organization only when an
organization_supplier link exists for it. Cross-organization
GET / PATCH / DELETE returns 404 rather than 403 so existence
isn't leaked.
Required scopes:
parties:readfor list / get,parties:writefor create / patch / delete. Unscoped keys (legacy) retain full access.