Skip to main content
All CollectionsApideck Unify
Sage Intacct: How to Use Apideck’s Proxy API for SOAP Requests
Sage Intacct: How to Use Apideck’s Proxy API for SOAP Requests

This guide explains how to set up and execute SOAP queries, using Apideck’s Proxy API to interact with Sage Intacct’s SOAP interface seamlessly.

Updated over a month ago

Why Use Apideck’s Proxy API?

Apideck’s Proxy API serves as an intermediary, enabling direct SOAP requests to Sage Intacct via the x-apideck-downstream-url header. This setup simplifies authorization and integrates easily with your existing Apideck connection, providing a straightforward way to send requests to Sage Intacct’s SOAP API.

Setting Up the Proxy for Sage Intacct

For each request sent through the Apideck Proxy API, you need to set the x-apideck-downstream-url header to point to Sage Intacct’s SOAP endpoint: https://api.intacct.com/ia/xml/xmlgw.phtml

This URL will remain the same for all queries directed to Sage Intacct via Apideck’s Proxy API.


​Sample Request

Below is an XML example to query sales order entries in Sage Intacct, retrieving fields such as RECORDNO, DOCNO, and DOCID. Note that the placeholders in curly braces—such as {sender_id}, {sender_password}, and {access_token}—should remain as-is to allow Apideck’s product to interpret them dynamically.

XML Request Body Example

<request> <control> <senderid>{sender_id}</senderid> <password>{sender_password}</password> <controlid>root</controlid> <uniqueid>false</uniqueid> <dtdversion>3.0</dtdversion> <includewhitespace>false</includewhitespace> </control> <operation> <authentication> <sessionid>{access_token}</sessionid> </authentication> <content> <function controlid="query"> <query> <object>SODOCUMENT</object> <select> <field>RECORDNO</field> <field>DOCNO</field> <field>DOCID</field> </select> <pagesize>200</pagesize> <offset>200</offset> </query> </function> </content> </operation> </request>

Executing the Query Using CURL with Apideck Proxy

To execute this request via the Apideck Proxy API, use the CURL command below. Replace the following values in the command:

  • YOUR_CONSUMER_ID: Your Apideck consumer ID

  • YOUR_APP_ID: Your Apideck app ID

  • YOUR_API_KEY: Your Apideck API key

Be sure to keep the placeholders (such as {sender_id}, {sender_password}, and {access_token}) in curly braces as-is for Apideck to handle dynamically.

Key Points

  1. Consistent Downstream URL: Always set x-apideck-downstream-url to https://api.intacct.com/ia/xml/xmlgw.phtml.

  2. Dynamic Placeholders: Keep placeholders like {sender_id}, {sender_password}, and {access_token} as they are for Apideck to replace these with the appropriate values during execution.

  3. Replace the request headers with your credentials: consumer_key, app_id and api_key
    Following this setup, you can efficiently use Apideck’s Proxy API to make SOAP queries to Sage Intacct, making data retrieval and management straightforward.

Did this answer your question?