ABL Soft API

Finance
Download This Spec

About this spec

The ABLSoft Radar API exposes selected pieces of information via a standardized programmatic interface. This is an enterprise API and it is assumed that prior to use of the Radar API your company has access or permission to access an existing Radar system. If you do not have access to an instance of Radar please contact your ABLSoft representative for more information. If you have access to a Radar system, but cannot consume the API contact your ABLSoft representative for information on enabling these services. These examples serve as a starting point to familiarize yourself with some of the capabilities of the ABLSoft Radar API. Custom API's and changes to the existing API's can be provided upon request. Contact your ABLSoft representative if you do not see your desired API available. If you have technical questions about the API please email your questions to techsupport@ablsoft.com. The API is accessed by making HTTP requests to a specific endpoint URL, in which GET or POST variables contain information about what you wish to access. Every endpoint is accessed via an SSL-enabled HTTPS (port 443) using OAuth2, Radar currently supports the OAuth2 Password Grant Type. Application developers must first obtain their CLIENT ID and SECRET CODE. This along with a valid username, password and appropriate security role to the specific Radar instance is required in order to obtain a unique OAuth2 token. To receive your assigned credentials, please contact technical support or your companies system administrator. Because all transactions are secured using the OAuth2 protocol, a valid token must first be obtained by passing the correct authentication credentials to the Radar application server. Upon successfully validating the credentials, the Radar system will return a unique OAuth2 token. This token can then be used repeatedly by the calling application to access Radar resources. Applications should store the token for later use to avoid repeating the user id and password steps in the future. Tokens expire after 1 hours; use the refresh token, or a previously generated refresh token, to retrieve a new access token when the first token expires. First, use the GET refresh token service along with your Radar credentials, retrieve the refresh token. Request: <code>$ curl --user MYCLIENTID:MYSECRETCODE https://mycompany.ablsoft.com/restapi/oauth/token -d username=myID -d password=myPWD -d grant_type=password</code> Response: <code>{"access_token":"bc156287-4662-4d5e-8c9d-51be256bda7d","token_type":"bear er","refresh_token":"368b1c65-d7a4-4eb3-9b23-c161df7262cb","expires_in":359 9,"scope":"read write"</code> Next, use the previously obtained refresh token to generate an access token. Request: <code>curl --user MYCLIENTID:MYSECRETCODE https://mycompany.ablsoft.com/restapi/oauth/token -d grant_type=refresh_token -d refresh_token=368b1c65-d7a4-4eb3-9b23-c161df7262cb</code> This access token will be used for authorization for all other API requests. As mentioned earlier, each client application must have its own unique login id and password to interface with the Radar API. The ID assigned is also tied to a security role that determines what resources the application will have access to. If you do not have access to a specific resource, contact your ABLSoft representative. To interface with a Radar web service, an HTTPS request must be formatted with the appropriate parameters as expected by the method in question. Radar web services return JSON objects by default. Depending on the method called, the JSON returned could either be a list or a single object. ABLSoft recommends testing API connectivity using the <a href="https://www.getpostman.com/docs/v6/">Postman client</a>.

About Versori

Versori has established itself as the third generation of Integration Platform as a Service (iPaaS). Versori builds custom integrations for its customers using an intuitive visual user interface.

Versori’s connector engine means there is no dependency on an existing library of apps, all you need to start is the documentation of the app or system you want to integrate to.

How can I integrate with this spec?

Upload your spec

Drag and drop the Open API Spec into Versori's connector engine to create a new connector in minutes.

Build your workflow

Build out visual integration workflows with powerful data tools on an intuitive canvas UI.

Deploy instantly

Deploy your automated workflow instantly and maintain your integrations with ease.

Issue with this spec?

Is there something wrong with this spec? Let us know and Versori's engineering team will improve the quality of the spec based on your feedback.

Report This Spec
Built for Security & Scale

How developers maximise their time & productivity with Versori

Easily map complex data fields

Automatically match and transform data fields between systems with precision, reducing manual effort and errors.

Build, integrate & deploy faster

Design integrations visually, test workflows instantly, and deploy seamlessly—accelerating your time to value.

Create any custom connector in minutes

Drag and drop API specifications to build custom integrations, unlocking endless connectivity with minimal setup.

Start building today

Ready to start integrating?

Google Ads
Batch
Dropbox
Airtable
Asana
Calendly
Filter