Recent changes to this query, from the audit log: the last 20 in 90 days, newest first. Readable by whoever can read the query; IP addresses and the full-history query only for owners and admins. New changes can take a few minutes to appear.
curl -X GET "https://example.com/queries/string/activity"{ "audit_query": "string", "data": [ { "action": "string", "actor": { "kind": "person", "name": "string", "user_id": "string" }, "ip": "string", "outcome": "ok", "time": "string" } ]}`PUT /organizations/{id}` — update an organisation. Slug + plan-tier changes are permitted; `data_lake_bucket` is system-managed and remains untouched by this endpoint. PUT
Previous Page
`POST /queries/compile` — compile VFQL and return the SQL or the diagnostics. POST
**Creates nothing** (R4): no run, no scheduler dispatch, no credit movement. A refused compile is a **200** carrying `diagnostics` and no `sql` — the request asked "is this valid, and where is it wrong?" and got its answer. The **400** is for an unknown `vfql_version`, which is a fact about the request with no place in the text to point at, and it carries no `diagnostics` key at all (R6). ⚠️ **No `?as_admin=` parameter, unlike every other route in this cluster.** This endpoint's job is to report catalog facts back to the caller, so an override here would be an unaudited catalog-disclosure surface; the catalog is always computed for the acting team with no admin clause (`vigilfield_query::compile_query_for`).