Use this article when a submit request is rejected, a job fails or never finishes, a result looks wrong, or a status or results request returns an error. A rejection at submit returns a 4xx with an...
The query engine infers column names and types every time it reads a CSV or JSON file — that inference is how file reading works, not a setting you turn on. What you control is how it infers, throu...
Run a SQL statement against files in Celigo Storage and read the results back as JSON rows. You write a SELECT statement that references a file or a folder by its storage path, submit it as a query...
Start a flow from the rows of a Celigo Storage query. You create an export on a Celigo APIs connection that submits the query, and you attach an async helper that polls the job and fetches its resu...
The Celigo Storage query API accepts one SQL statement and runs it against files in Celigo Storage as an asynchronous job: you submit the query, poll the job's status, and fetch the result one page...
Celigo SQL is the SQL dialect you use to query Celigo Storage files. It's a curated subset of standard SQL, PostgreSQL-compatible where syntax is otherwise ambiguous, with the exceptions documented...
The Celigo Storage query API lets you run SQL against files that are already in Celigo Storage and read the results back as JSON rows. You send one SELECT statement to the query API, point it at a ...
Topics are governed the same way connections are: they are account-level resources that you register to the integrations that use them, and registration determines which users can see and manage ea...
Assign a network policy to control where an MCP server, an API token, workspace-user sign-in, or end-user authentication can be reached from. Each server, token, and restriction holds one policy, a...
Create a network policy once, then assign it to MCP servers, API tokens, workspace-user sign-in, or end-user authentication. This article covers creating, editing, and deleting a policy, and viewin...