Can I connect a JSON file to iDBQuery?

A JSON file connects to iDBQuery as a file data source — no database or API needed.

• You'd connect it by uploading or pointing iDBQuery at the .json file (an export, an API dump, a log extract).
• iDBQuery flattens the nested structure into queryable rows and columns, applies its semantic layer to the field names, and adds it to your one live queryable model.
• Ask in plain language — *"How many records have status = failed, grouped by type?"* — and iDBQuery writes and runs the query, returning a cited number, chart or table.

JSON is a common way to hand iDBQuery a slice of data that lives between systems — an export from an app, a webhook payload, a config dump. Once it's in the model, you can combine that JSON with a database, a warehouse or a spreadsheet in a single question, reasoned over as one model with no pipeline. And because every figure is cited back to the exact record, even an ad-hoc file produces auditable answers. If the JSON is coming from a live endpoint rather than a file, use the REST API connector instead so it can refresh on a schedule. Sensitive files stay local with the Desktop app or an air-gapped deployment.