Skip to content
Analytics & data warehouses

powerbi.com

Test against the Power BI REST API

A hosted, stateful simulation shaped like the Power BI REST API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with powerbi.com.

Operations
27
example request
curl https://your-power-bi.slurry.io/v1.0/myorg/groups \
  -H "Authorization: Bearer slurry_sim_live_..."

Your simulation gets its own hostname, key and IP allow-list. Spec snapshot: version v1.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 27.

  • GET/v1.0/myorg/datasets
  • POST/v1.0/myorg/datasets
  • GET/v1.0/myorg/datasets/{datasetId}
  • PATCH/v1.0/myorg/datasets/{datasetId}
  • DELETE/v1.0/myorg/datasets/{datasetId}
  • POST/v1.0/myorg/datasets/{datasetId}/executeQueries
  • GET/v1.0/myorg/datasets/{datasetId}/refreshes
  • POST/v1.0/myorg/datasets/{datasetId}/refreshes
  • GET/v1.0/myorg/reports
  • GET/v1.0/myorg/reports/{reportId}
  • DELETE/v1.0/myorg/reports/{reportId}
  • GET/v1.0/myorg/groups/{groupId}/datasets

Does this simulation differ from the real Power BI REST API?

Tell us about wrong response shapes, status codes, missing endpoints or unrealistic data. If you have a simulation of it, report from its Issues tab so we can see the exact call.