Question 1

What APIs can I connect?

Accepted Answer

Any HTTPS REST or GraphQL API. Configure the base URL, auth format, and required headers in the TextQL admin console. Whitelist the target domain, store any secrets in the vault, and Ana can start calling the API immediately from its Python sandbox without writing code.

Question 2

Which auth formats are supported?

Accepted Answer

Bearer tokens in the Authorization header, custom API key headers like X-API-Key, basic auth with username and password, and OAuth 2.0 client credentials flows. For custom auth schemes not in this list, contact TextQL — we can often add them as first-class options quickly.

Question 3

How is the custom API secured?

Accepted Answer

Custom APIs use the same security model as built-in connectors. The domain must be explicitly whitelisted, secrets are encrypted in TextQL's credential vault, and values are injected at the network layer by our egress proxy. Ana's Python sandbox never sees raw credentials.

Question 4

Can I call multiple custom APIs?

Accepted Answer

Yes. Configure as many Custom API connectors as you need, each with its own domain, auth, and headers. Ana treats each as an independent source and can join responses from multiple custom APIs and your warehouse in a single question.

Question 5

Is there rate limiting?

Accepted Answer

TextQL applies sensible default rate limits per connector to prevent runaway calls. Admins can adjust limits per custom API if your endpoint supports higher throughput. Ana also honors HTTP 429 responses with automatic exponential backoff for resilience.