Ignition

The INDAQ JDBC driver lets an Ignition gateway query your INDAQ data the same way it queries any SQL database. Once it is set up you can use INDAQ in Named Queries, query bindings, scripts and reports.

The driver is read-only. It connects to INDAQ over HTTPS, so the gateway never needs a direct connection to your equipment or your INDAQ Interface.

Before you begin

You will need:

• An Ignition 8.1 or 8.3 gateway, and a user that is allowed to change its configuration. The screenshots in this guide are from Ignition 8.3, and the differences for 8.1 are called out where they matter.
• An INDAQ user with the Manager role or above in your organization, to create the API key the gateway will sign in with.
• Outbound HTTPS (port 443) access from the gateway to api.indaq.cloud.

Download the driver

The driver is a single .jar file of about 76 KB. It has no other dependencies, so there is nothing else to install alongside it.

If you would like to verify the download, the SHA-256 checksum of indaq-jdbc-0.1.0-SNAPSHOT.jar is:

485ce0cbb80f56bbb9894ba690977b39dfe82b18a38a048988174d7931a91e8f

Create an API key

The gateway signs in to INDAQ with an API key rather than with your own account. A key is limited to one organization, can be limited further to a single project, and can be revoked at any time without affecting anyone's login.

1. Sign in to INDAQ and open your organization's Settings.
2. Select API Keys, then Create API Key.
3. Give the key a Name that says where it will be used, such as Ignition — Press Line 1.
4. Choose the Project the gateway should read from. Leaving this empty allows the key to read every project in the organization.
5. Choose when the key Expires, then select Create.

INDAQ then shows the key's Username, which begins with indaq_sk_, and its Password. Keep this window open, or copy both values somewhere safe, until you have finished setting up the connection.

Add the driver to Ignition

This step tells Ignition about the INDAQ driver. It only needs to be done once per gateway.

Create the driver

1. In the gateway, go to Connections, then Databases, then Settings, and make sure the Drivers tab is selected.
2. Select Create JDBC Driver.
3. Under General, fill in:

4. Scroll down to Driver & Default Instructions and fill in:

5. Select Create JDBC Driver.

Upload the driver file

The driver is not installed until Ignition has the .jar file you downloaded.

1. On the Drivers tab, open the three dots menu at the end of the INDAQ row and select Manage JAR Files.

2. Select Choose File(s), pick indaq-jdbc-0.1.0-SNAPSHOT.jar, and then select Save Changes.

The INDAQ row should now show the driver's version and a status of Installed.

Ignition 8.1

On Ignition 8.1 the driver and its file are added together:

1. In the gateway, go to the Config section, then Databases, then Drivers.
2. Select Create new JDBC Driver... at the bottom of the page.
3. Choose indaq-jdbc-0.1.0-SNAPSHOT.jar in the JAR File(s) field, and fill in the other fields with the same values as the tables above.
4. Select Create New JDBC Driver.

Create the database connection

1. In the gateway, go to Connections, then Databases, then Connections, and select Create Database Connection.
2. Select INDAQ as the driver, then Next.

3. Fill in the connection:

4. Select Create Database Connection.

After a few seconds, the new connection should show a status of Valid.

Finding your Connect URL

The Connect URL names the organization and the project that the connection will read from:

jdbc:indaq://api.indaq.cloud/<organization>/<project>

Both values can be read from your browser's address bar while you have the project open in INDAQ:

https://indaq.app/orgs/<organization>/<project>/charts

• <organization> is your organization's short name, such as my-organization.
• <project> is the project's number, such as 1042. The project's name cannot be used here.

If your API key is limited to a single project, the Connect URL has to name that same project.

Connection options

Options can be added to the end of the Connect URL, for example jdbc:indaq://api.indaq.cloud/my-organization/1042?queryTimeout=30&strictNames=true.

Querying your data

The quickest way to check that everything works is the Database Query Browser in the Ignition Designer. Select your INDAQ connection and run:

SELECT parameter_id, name, interface_name, interval_secs FROM parameters

INDAQ presents your project as three kinds of table.

parameters

One row for each Parameter in the project. Use it to look up the parameter_id of the values you want to query.

data

One row for each reading, exactly as it was recorded.

SELECT ts, value FROM data
 WHERE parameter_id = 1042
   AND ts >= '2026-08-01' AND ts < '2026-08-02'
 ORDER BY ts

To bring a long time range down to a size suitable for a chart, group the readings into buckets. time_bucket takes a width in seconds, and avg, min, max, sum, count, first and last are available.

SELECT time_bucket(ts, 900) AS bucket, parameter_id, avg(value), min(value), max(value)
  FROM data
 WHERE parameter_id IN (1042, 1043)
   AND ts >= '2026-08-01' AND ts < '2026-08-08'
 GROUP BY 1, 2
 ORDER BY 1

Interface tables

Each Interface is also available as its own table, named after the Interface, with a ts column followed by one column per Parameter. This is usually the most convenient shape for a chart or a table component.

SELECT ts, "Motor Temp", "Line Speed"
  FROM "Press Line 1"
 WHERE ts >= '2026-08-01' AND ts < '2026-08-02'

Parameters are recorded independently of one another, so their readings rarely share an exact timestamp. INDAQ lines them up into shared time buckets for you, and a Parameter with no reading in a bucket is returned as NULL. The align connection option controls how this is done.

Using INDAQ in scripts

Named Queries and system.db.runPrepQuery both work, including ? placeholders:

end = system.date.now()
start = system.date.addHours(end, -8)

rows = system.db.runPrepQuery(
    "SELECT ts, value FROM data WHERE parameter_id = ? AND ts >= ? AND ts < ? ORDER BY ts",
    [1042, start, end],
    "INDAQ",
)

Things to keep in mind

• Always give a time range. Include both a start and an end for ts in every query against data or an Interface table. A query without one is limited to a default window and returns a warning.
• Parameter names can repeat. INDAQ allows two Parameters to share a name, so WHERE parameter_name = 'Motor Temp' can return more than one series. Filter by parameter_id, or turn on the strictNames option.
• Times are in UTC, to the nearest second.
• Queries are kept simple. JOIN, subqueries, UNION, DISTINCT, HAVING, OFFSET and filtering on value are not supported, and results can only be ordered by ts. The error returned by an unsupported query explains what to change.
• Limits apply. Each API key may run 600 queries per minute, an organization may run 4 queries at the same time, a query may run for up to 60 seconds, and a result may contain up to one million rows.

Troubleshooting

The connection is faulted with "SELECT requires a FROM clause"

The connection is still using Ignition's default validation query. Edit the connection, select Show Advanced, and set Validation Query to SELECT parameter_id FROM parameters LIMIT 1. Setting the Default Validation Query on the driver, as described above, fixes this for any connection created afterwards.

The connection is faulted with "JDBC URL must name a project"

The Connect URL is missing its last part. It has to contain both the organization and the project number. See Finding your Connect URL.

The connection is faulted and the username or password is rejected

Check that the Username is the complete value beginning with indaq_sk_, and that the key has not expired or been revoked on the API Keys page. A key that is limited to one project will also be rejected by a Connect URL that names a different project. Because the password cannot be looked up again, the quickest fix is often to create a new key.

The connection times out

The gateway cannot reach INDAQ. Confirm that the gateway's network allows outbound HTTPS to api.indaq.cloud on port 443, including through any proxy or firewall between the gateway and the internet.

INDAQ cannot be selected when creating a connection

Ignition greys out any driver whose .jar file is missing. The driver has been created, but its file has not been uploaded or the upload was not saved. Return to Upload the driver file and confirm the driver's status is Installed.

If you are still having trouble, contact support and we will be happy to help.