Ready to get started?

Learn more about the Authorize.Net MuleSoft Anypoint Connector or download a free trial:

Download Now

Access Authorize.Net Data in Anypoint Using SQL

Create a simple Mule Application that uses HTTP and SQL with the CData Mule Connector for Authorize.Net to create a JSON endpoint for Authorize.Net data.

The CData Mule Connector for Authorize.Net connects Authorize.Net data to Mule applications enabling read functionality with familiar SQL queries. The Connector allows users to easily create Mule Applications to backup, transform, report, and analyze Authorize.Net data.

This article demonstrates how to use the CData Mule Connector for Authorize.Net inside of a Mule project to create a Web interface for Authorize.Net data. The application created allows you to request Authorize.Net data using an HTTP request and have the results returned as JSON. The exact same procedure outlined below can be used with any CData Mule Connector to create a Web interface for the 170+ available data sources.

  1. Create a new Mule Project in Anypoint Studio.
  2. Add an HTTP Connector to the Message Flow.
  3. Configure the address for the HTTP Connector.
  4. Add a CData Authorize.Net Connector to the same flow, after the HTTP Connector.
  5. Create a new Connection (or edit an existing one) and configure the properties to connect to Authorize.Net (see below). Once the connection is configured, click Test Connection to ensure the connectivity to Authorize.Net.

    You can obtain the necessary connection properties on the Security Settings -> General Settings page after logging into your Merchant Account.

    • UseSandbox: The Authorize.Net API to be used to process transactions. If you are using a production account, this property can be left blank. If you are using a developer test account, set this to 'TRUE'.
    • LoginID: The API login Id associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions. Note that this value is not the same as the login Id that you use to log in to the Merchant Interface.
    • TransactionKey: The transaction key associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions.
  6. Configure the CData Authorize.Net Connector.
    1. Set the Operation to 'Select with Streaming'.
    2. Set the Query type to Dynamic.
    3. Set the SQL query to SELECT * FROM #[message.inboundProperties.'http.query.params'.get('table')] to parse the URL parameter table and use it as the target of the SELECT query. You can customize the query further by referencing other potential URL parameters.
  7. Add a Transform Message Component to the flow.
    1. Map the Payload from the input to the Map in the output.
    2. Set the Output script to the following to convert the payload to JSON:
      %dw 1.0
      %output application/json
      ---
      payload
              
  8. To view your Authorize.Net data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default) and pass a table name as the table URL parameter: http://localhost:8081?table=SettledBatchList
    The SettledBatchList data is available as JSON in your Web browser and any other tools capable of consuming JSON endpoints.

At this point, you have a simple Web interface for working with Authorize.Net data (as JSON data) in custom apps and a wide variety of BI, reporting, and ETL tools. Download a free, 30 day trial of the Mule Connector for Authorize.Net and see the CData difference in your Mule Applications today.