Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-09-08

Endpoint: GET /api/v1/odata (service document)

Reference for the OData v4 service document — lists the entities (gold/silver tables) that Power BI and Excel discover to consume the datalake.

On this page (8)

The service document is the entry point of the OData v4 feed: it lists one entity per published table (*_gold/*_silver) in the workspace. Power BI and Excel discover the feeds from here.

Summary#

Method · routeGET /api/v1/odata
Basehttps://ingestia.io
AuthAPI key (Authorization: Bearer ing_live_… or ?api_key=)
Role (RBAC)data export (member+); data key = owner
CostR$ 0 (discovering entities does not trigger a paid job)
HeadersOData-Version: 4.0 · X-Ingestia-Access-Scope: workspace
Statuses200 · 401 · 403 · 429 · 402 · 503

Parameters#

None. It also responds to OPTIONS (CORS preflight).

Example#

curl -H "Authorization: Bearer ing_live_EXEMPLO" \
  https://ingestia.io/api/v1/odata

200 response#

json
{
  "@odata.context": "https://ingestia.io/api/v1/odata/$metadata",
  "value": [
    { "name": "vendas", "kind": "EntitySet", "url": "vendas" }
  ]
}

For the column types (EDMX), see GET /api/v1/odata/$metadata.

Notes#

  • The entities in the service document are identical to those in $metadata — same governance allowlist (PII excluded, always).
  • With no datalake provisioned, the feed responds 503 in production (it never fakes).

Errors#

CodeWhen
401missing/invalid key
403insufficient role/scope
429 · 402rate limit (120/min per key) / overdue payment
503datalake not provisioned / own cloud down / limiter unavailable

Security#

  • Read-only, scoped to the workspace (published marts only).
  • PII columns do not appear in the service document or in $metadata.

Related#


Last reviewed: 2026-09-08.

Related links