A tool helps the developers to construct and post Sage Intacct web-service API requests easily and intuitively.
Users can fill in the Intacct instance credentials in the Configurations screen and make the API calls without having to save the credentials and also without logging into the app.
- Users can build and post the API requests directly. The app does not force users to log in to test some API requests quickly.
- Data is secure, as the sensitive data is not stored locally (or anywhere else) in this approach.
- Intacct instance credentials entered on the
Configurationscreen is used to form the<control>and<authentication>sections of the API request.
The downside of this approach is - "Configuration data reuse" and "Request history" features of the apps cannot be used. Check-out the below sections to see how you can use this app effectively by utilizing both the feature.
Create a user and save the Intacct instance credentials on your browser locally in a secure way.
- Authentication for data access: The user needs to login with his master password to access the Intacct instance credentials data. The user session ends on either logout or closing the browser.
- Data is secure: The sensitive data are stored locally using a highly secured data encryption mechanism.
- Data re-use: Users can select the desired Intacct instance credentials from the
Saved Configurationsdropdown list. - Labeling the data: Users can name the credentials-set with a custom name!
- Easier to manage the data: One place for managing the Intacct instance credentials data. You can add and modify the credentials. Also, there are options to clear and delete the credentials.
- The app user's master password hashed with the SHA3 algorithm. A random (512/8) salt generated along with the password hash. These password hash and salt are then used to create the encryption key (512/32) with the PBKDF2 algorithm.
- Sensitive data like Intacct user passwords and sender passwords are encrypted in AES encryption with the encryption key and are saved locally (on the local storage of the browser).
Users can select the objects associated with an instance dynamically.
- Once you switch over to the
API 3.0tab, the corresponding objects (of the selected Intacct instance credentials) get auto-populated in theSelect Objectdropdown field. This helps users to choose the desired object dynamically (even the custom objects of the instance) rather than a static list of objects.
- A meta-data API query fetches the list of objects (including custom objects) and populates the
Select objectdropdown field.
Users can dynamically select the methods associated with an object.
- The user is allowed to select the methods associated with the selected object. More importantly, this helps users to run the generic methods like getAPISession, getUserPermission, installApp, etc.., which do not need the object context!
- When the object is not selected, the
Select Generic Methoddropdown shows up with generic method names.
Once a particular object and method are selected, the corresponding request template gets loaded by the app. This template acts as a skeleton for you to build your complete request.
- Helps user to build the request XML with a request template for the selected object and method
- A request template got generated for a selected method. The corresponding object value gets substituted in the request template.
Users can build the query dynamically by selecting the field and value using the interactive query builder tool.
- The app helps users to build the query dynamically for the selected object and criteria. This intuitive UI tool helps to construct the query using clicks rather than writing the cryptic query string.
- Users get an option to build the query using a construct query tool. By this, one can add or chain the multiple query criteria. A dynamic query string is constructedUsing the field and value combination of the query. Finally, the request template gets substituted with the dynamic query before posting the API request.
The
select fieldssection gets enabled on the click of the+ Show Fieldsbutton. Here this allows the users to select the fields to be included in the response.
Users can build the create and update requests dynamically by selecting the field and value using the interactive request builder tool.
- Helps to build the create and update request XML dynamically for the selected object, field, and values. Again, this intuitive UI tool assists the users to construct the request using clicks rather than writing the cryptic XML payload.
- Users provided with an option to build the request XML for create and update methods using
select fieldsandput value in the fieldsUI sections. By this, one can select and provide value to the fields. A request XML is constructed using the selected field-value combination. Finally, the request template is substituted with the dynamic request XML.
Required fields are pre-selected (and obviously, disabled to deselect) in the
select fieldssection of the screen. Mouse-hover on the field displays meta-data info of the same.
Have the flexibility to edit and format the API requests manually and post.
- Allows the user to edit the request XML that the tool has generated, so that the user can overwrite and modify the request XML to his needs.
- If the changes are done manually by editing the request XML, you can click on the
Formatbutton to arrange the XML in a nicely indented format.
- The format button beatifies the XML data.
Have a flexibility view and copy the API request and response.
- Allow the users to view the API response once received. Users can select and copy the response from the
API Responsetab. - Also, there's an
API Requesttab to show the complete API request (including the control and authentication blocks) posted by the user. - The response metrics such as
Post URL,Response Time, andStatus Codeare also shown for each API response.
- Both request and response data are formatted and presented in different sections for transparency.
Users can see the last 30 API requests stored in the Request history (a table in local storage).
- The app allows the users to navigate and view the previous requests and reuse them. Also, users can load the previous requests and make modifications by overwriting them.
- Once a request is posted, the app stores the content part of the API request in a table of the local storage. This table can hold a maximum of up to 30 requests. It works on a circular queue approach.
There are also options to navigate to the first and last requests of the Request history queue.
Users can also build and post the legacy API (v-2.1) requests.
- The app allows the user to build and post API version-2.1 requests if needed.
- Go to the
API-2.1tab and build the request XML.
Request History of API-3.0 and API-2.1 are separate!
To install the extension into Chrome (tested on Version 44.0.2403.125 m)
-
Download the source zip file using below URL and extract it :
https://github.com/sharat-developer/Intacct-InteractiveAPITool/archive/master.zip
or checkout via git
git clone https://github.com/sharat-developer/Intacct-InteractiveAPITool.git -
In Chrome, go to "chrome://extensions/"
-
Enable "Developer Mode" via the checkbox at the top
-
Click the "Load unpacked extension..." button and select the folder where you extracted the zip file
- Launch "InteractiveAPITool" from Chrome Apps
- Key-in your Company configuration details then go to API-3.0 and API-2.1 Tabs for Building and Posting API Requests.
- If you want store the Company configuration for later use, click on "Save" button which opens a login pop-up.
- Click on "Need an Account?" link and sign-up for creating an account.
-
jQuery License - https://github.com/jquery/jquery/blob/master/LICENSE.txt
-
Twitter Bootstrap License - https://github.com/twbs/bootstrap/blob/master/LICENSE
-
CryptoJS License - https://code.google.com/archive/p/crypto-js/wikis/License.wiki










