Capabilities Data services

Read and write any combination of fields, through REST, SOAP or SQL, under one policy.

Every door into the data bed goes through the same policy engine: REST for applications, SOAP with a WSDL generated from the model for older integrations, SQL through JDBC and ODBC for BI and analysts, events for consumers that sync, files for exchange, and an agent endpoint.

RESTGET · PUT · PATCHSOAPWSDL from modelSQLJDBC · ODBCEventswebhooks · KafkaFilesCSV · ParquetMCPagents · copilotsOne policy enginerow · column · cellread · write · deleteaudited onceThe data bedreference · hierarchy · dimensionmaster · transactionany combination of fields, any depthTHE SAME CALL, THREE WAYSGET /api/v1/supplier?fields=legal_name,vat_id,payment_terms&filter=country:DE&expand=open_posSELECT legal_name, vat_id, payment_terms FROM golden.supplier WHERE country='DE'<sup:select><sup:fields>legal_name vat_id payment_terms</sup:fields><sup:where>country=DE</sup:where></sup:select>
Six doors, one policy engine, one bed. The same request in REST, SQL and SOAP.
6
doors: REST, SOAP, SQL, events, files, agents
product
1
policy engine under all of them
product
any
combination of fields, any depth
product
100%
of writes validated by the rules and acknowledged
product
Step by step

How a PUT of three fields is handled

The caller names the fieldsPUT /api/v1/golden/supplier/L-00731 with payment_terms, contact_email and a site address; nothing else.
The doors

What each one is for

DoorForReadWrite
RESTapplications, portals, SmartAppsGET with fields=, filter=, expand=, as_of=; pagination and limits publishedPUT and PATCH on any combination; POST to create or propose
SOAPolder integrations and middlewareselect operations generated from the model (WSDL)insert and update operations, bulk or per record
SQL (JDBC · ODBC)BI tools, analysts, spreadsheetsgolden views and the bed, with AS OFgoverned data entry through the workbench; bulk as a table
Eventsconsumers that syncwebhooks and Kafka topics per domain: created, changed, merged, retired—
Filesexchange with partners and legacy systemsgoverned extracts with the security filters applied and loggedloads with the same rules as any other write
Agent endpoint (MCP)copilots and agentsthe same reads as REST, as the agent's identityproposals, logged at the agent's level
Any combination, any depth

One field-selection syntax everywhere

The fields parameter takes any list of attributes, nested groups and related objects: legal_name, vat_id, sites.address.postcode, open_pos.count. The same syntax works in REST, in the SOAP select operation and as a column list in SQL, so an integration written once reads the same shape from every door.

Bulk is a table: a bulk read is a SQL query or a paged GET; a bulk write is a load with the same rules as a single PUT. There is no separate job API with its own limits.

# three doors, one shape
GET /api/v1/golden/supplier?fields=legal_name,vat_id,sites.address.postcode,open_pos.count&filter=country:DE

SELECT legal_name, vat_id, sites.address.postcode, open_pos.count
FROM golden.supplier WHERE country = 'DE';

<sup:select><sup:fields>legal_name vat_id sites.address.postcode open_pos.count</sup:fields>
  <sup:where>country=DE</sup:where></sup:select>
Terms on this page

Data serviceA REST, SOAP or SQL door through which any combination of fields can be read or written under the same policy.
WSDLThe description of a SOAP service; here generated from the domain model.
Freshness contractThe stated rule for how current a column is: live, cached for a number of minutes, or replica with its batch.
Questions

Do SOAP consumers get the same security?

Yes; the WSDL operations run through the same engine as REST and SQL.

How are events kept complete?

Change events come from the ledger, so source-side changes read in place and hub-side edits both fire; a consumer can replay from any point.

Can a partner receive a file with masked values?

Yes; an extract runs as the partner's identity, so masks and row filters apply, and the extract is logged.

See your first domain built on your data

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.