dSilo
Data API Hub
Customer-facing UAT portal for the dSilo Data-as-a-Service API.
Discover how authentication, required headers, and the contracts and invoices summary endpoints work before you call the gateway.
Gateway: https://dsilo-apim-stage-01.azure-api.net/dsilo/
Start with authentication and headers, then call the summary APIs.
1. Authenticate
Request an Entra ID access token with client credentials and the Data.Read app role. Use only the access_token value on API calls.
2. Required headers
Send Authorization (Bearer), Ocp-Apim-Subscription-Key, and x-api-key on every call. Set Accept and Content-Type; never paste live secrets.
3. Call the API
POST to the UAT gateway summary endpoints with JSON or Parquet Accept. Use the guides below for filters, response shape, and examples.
What you can call
Use the guides below for contracts and invoices summary calls, including filters, JSON envelope, and Parquet options.
POST /v1/contracts/summary
Returns allowlisted contract summary records. Filter with contractWorkspaceID, createdFrom/createdTo, updatedFrom/updatedTo, orderBy, and order (asc|desc). Date values are YYYY-MM-DD; From ≤ To; range must not exceed one month. JSON supports page and pageSize; do not send pagination with Parquet.
POST /v1/invoices/summary
Returns invoice summary records (and related invoiceTables when present). Filter with InvoiceId and the same date/order fields. Parquet Accept returns a zip containing invoices.parquet and invoice_tables.parquet.
JSON success shape: data (records), pagination (page, pageSize, totalRecords, totalPages, hasNext), and meta (requestId, generatedAt, optional warning). meta.requestId matches the X-Request-ID response header — use it for support.