Skip to main content
POST
RunQueryAPI mirrors the erdo_run_query MCP tool as a REST endpoint.

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Path Parameters

datasetSlug
string
required

Body

application/json
apply_default_filters
boolean

which has always supported this and which every internal admin/debug read already uses. External callers had no way to reach it, and that turned a default filter into something nobody outside Erdo could see past — including the person who created it.

That matters because default filters are how rows get hidden on purpose: test submissions, and now a lead somebody marked as never having been an enquiry. Hiding a row from the numbers is right; making it unreadable is not. Reviewing what you excluded, and deciding whether you were wrong, needs the row itself.

It is not an access bypass: RBAC decides who may read the dataset at all, and this only chooses whether a presentation default is applied to a read the caller is already entitled to make. Absent means true, so every existing caller is unaffected.

dataset_slug
string
filter_names
string[]
limit
integer<int64>
query
string
resource_key
string

Response

Success response

columns
string[]
row_count
integer<int64>
rows
string[][]