Ready to get started?

Connect to live data from Printful with the API Driver

Connect to Printful

Query Printful Data in ColdFusion



Write standard ColdFusion data access code to connect to Printful data.

The CData JDBC Driver for Printful seamlessly integrates connectivity to Printful data with the rapid development tools in ColdFusion. This article shows how to connect to Printful data in ColdFusion and query Printful tables.

Create a JDBC Data Source for Printful in ColdFusion

The JDBC data source enables you to execute SQL from standard ColdFusion tags like cfquery and CFScript like executeQuery.

  1. Copy the driver JAR and .lic file from the installation directory onto the ColdFusion classpath. For example, copy the files into C:\MyColdFusionDirectory\cfusion\wwwroot\WEB-INF\lib. Or, open the Java and JVM page in the ColdFusion Administrator and enter the path to the files in the ColdFusion Class Path box.

    The JAR and license for the driver are located in the lib subfolder of the installation directory.

    Restart the server after this step.

  2. Add the driver as a data source:

    From the ColdFusion administrator interface, expand the Data & Services node and click Data Sources. In the Add New Data Source section, enter a name for the data source and select Other in the Driver menu.

  3. Populate the driver properties:

    • JDBC URL: Enter connection properties in the JDBC URL. The JDBC URL begins with jdbc:api: and is followed by the connection properties in a semicolon-separated list of name=value pairs.

      Start by setting the Profile connection property to the location of the Printful Profile on disk (e.g. C:\profiles\Printful.apip). Next, set the ProfileSettings connection property to the connection string for Printful (see below).

      Printful API Profile Settings

      In order to authenticate to Printful, you'll need to provide your API Key. To get your API Key, first go to 'Settings' then 'Stores'. Select the Store you would like to connect to, then click the 'Add API Access' button to generate an API Key. Set the API Key in the ProfileSettings property to connect.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the Printful JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.api.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      A typical JDBC URL is below:

      jdbc:api:Profile=C:\profiles\Printful.apip;ProfileSettings='APIKey=my_api_key';
    • Driver Class: Enter the driver class. The driver class is cdata.jdbc.api.APIDriver.
    • Driver Name: Enter a user-defined name for the driver.
    • Username: Enter the username used to authenticate.
    • Password: Enter the password used to authenticate.

You can now test the connection by enabling the CData Printful data source in the Actions column. After reporting a status of OK, the Printful data source is ready for use.

Execute Queries

The cfquery tag can pass SQL statements to Printful. Use the cfqueryparam tag to create parameterized queries and prevent SQL injection through the query string.

Note: To use the cfquery and cfscript, create a .cfm file. Inside the .cfm file, write the code to execute the query (see below). Place the file directly in the root directory of your web server (e.g., wwwroot in Adobe ColdFusion). Restart the service after placing the file for the changes to take effect.

<cfquery name="APIQuery" dataSource="CDataAPI"> SELECT * FROM Orders WHERE Status = <cfqueryparam value="#Status#" cfsqltype="cf_sql_varchar"> </cfquery> <cfdump var="#APIQuery#">

Below is the equivalent in CFScript:


<cfscript>
result = queryExecute(
  "SELECT * FROM Orders WHERE Status = ?", 
  [
    { value="inprocess", cfsqltype="cf_sql_varchar" }
  ],
  { datasource="CDataAPI" }
);

writeDump( var= result );
</cfscript> 

You can then make requests to your .cfm like the following:

http://MyServer:8500/query.cfm?Status=inprocess