A satellite application, a portal, a planning system or an agent sends the attributes it has (a name, a country, a tax number, a part number) and receives the golden id, the record, the cross-reference and, on request, live related facts such as open orders.
# the portal asks with what it knows POST /api/v1/golden/supplier/lookup { "legal_name": "Acme Comp.", "country": "DE", "vat_id": "DE 812 345 678", "postcode": "71034", "expand": ["xref", "open_pos"] }
# Lima answers with the golden record 200 OK · 84 ms { "golden_id": "L-00731", "confidence": 0.97, "rule": "R-supplier-04 v3", "legal_name": "Acme Components GmbH", "lifecycle": "active", "xref": {"sap": "0000104471", "oracle": "300000098", "portal": "SUP-88213"}, "open_pos": {"count": 62, "value": 1200000, "currency": "EUR"} }
Confidence, rule and version are in every answer, so the caller can decide what to do below a score. Related facts come from the same bed through the cross-reference, live. The answer carries only the columns the caller's identity may see.
| Endpoint | Does | Notes |
|---|---|---|
| POST /golden/{domain}/lookup | match a payload; optionally create | confidence, rule, version; expand facts |
| GET /golden/{domain}/{id} | read a golden record | fields= selects any combination; as_of= for point in time |
| GET /golden/{domain}/by-source/{system}/{key} | read by a source key | the cross-reference resolves it |
| GET /golden/{domain}/{id}/related/{object} | live related facts | orders, invoices, tickets, hierarchy position |
| POST /golden/{domain}/{id}/propose | propose a change with evidence | enters the steward queue or applies within its allowed range |
| GET /golden/{domain}/changes?since= | changes since a time | for consumers that sync; no cap |
| POST /golden/{domain}/bulk-lookup | match a file of payloads | asynchronous; results per row with confidence |
Every endpoint publishes its page size, its rate limit and its freshness contract. Callers authenticate with OAuth 2.0 client credentials or a delegated user token, and the twelve security layers apply to the identity that calls.
Searches before it creates; shows the applicant whether the company is already a supplier.
Resolves item and site keys to golden ids before a load; asks for hierarchy positions.
Every screen bound to a golden record reads it through the same call, with the user's identity.
Ask for the golden record before acting; propose changes through the propose endpoint, logged at their level.
Look up a golden id from a name column; join live facts through SQL.
The golden record and the cross-reference are live; related facts follow their column's freshness contract (live, cached or replica), which the answer states.
The same operations are published as a WSDL generated from the domain model; see data services.
Per client, per endpoint, published in the developer portal; a client above its limit receives a clear answer and a retry time.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
