How do I connect a REST API that needs an API key or OAuth to iDBQuery?

Use iDBQuery's REST API connector: enter the endpoint and your authentication — an API key/bearer token or OAuth credentials — and iDBQuery calls the API, turns the responses into queryable tables, and adds them to one live queryable model you ask in plain language, with cited answers.

iDBQuery's REST API connector handles authenticated APIs, so you don't need a custom script or a pipeline to get an API's data into analysis.

  • Point and authenticate. Enter the endpoint URL and the API's auth — an API key / bearer token in a header, or an OAuth client credential / token flow. iDBQuery stores credentials securely (encrypted) and includes them on each call.
  • Shape the response. iDBQuery normalises the JSON responses — flattening nested fields and handling pagination — into queryable tables, and applies its semantic layer to the field names.
  • Ask in plain language. The API becomes part of your one live queryable model: iDBQuery writes and runs the query and returns a cited number, chart or dashboard.

This is the same connector used for SaaS tools like Salesforce, HubSpot, Stripe and Airtable — any product with a REST API. The differentiator is that the API's data doesn't sit in a silo: you can join it with your databases, warehouse and spreadsheets in a single question, one model, no ETL. Every figure is cited back to the source record, and you can schedule the source to refresh so answers stay current. There are safeguards against server-side request forgery (SSRF), and for sensitive integrations you can deploy in your own VPC or air-gapped so calls stay within your network.

Updated 2026-06-22