DATABASICS API

To learn about DATABASICS API please contact us to schedule a call with our development team.

To access API Documentation click here

Overview

The DATABASICS Time and Expense solution integrates with a broad range of travel, financial, and HR systems. As a result, you get a centralized solution with real-time visibility. The integration capabilities of DATABASICS answers your toughest business requirements and scales with you.

With the DATABASICS API, you have the power to develop custom integrations between DATABASICS Time & Expense and any other open application in your organization.

Some examples of what you can do with our REST-based API are:

• Log the time your support team spends resolving tickets into your service management system (e.g., Jira Service Desk).

• Re-route DATABASICS approvals based on Outlook “Out of Office” status.

• Build a project dashboard that supplements DATABASICS Time & Expense data with Other Direct Costs and Estimated Time to Complete.

• Incorporate Vacation Requests from DATABASICS Leave Management into your scheduling system.

• Download receipts by expense report or specific transaction.

• Import Clock In/Out Data from external devices.

In other words, our API lets you address your organization’s most specialized needs for time and expense data.

Open

The API Objects are organized similar to Admin Module:

• Organization

• WBS

• Time

• Expense

• Utilities

• Data Piping

• Security

Most of the functionality in admin are published as API functions.   You must login first in order to get a validate Session before you call any functions and pass session id, and once you are done make sure you logout.

IMPORTANT Note: Please be sure to use the logout method prior to creating any new login calls. Creating multiple login calls with failure to logout may cause your account to be suspended or deactivated. 

Important

• All Primary Codes fields size are 20 Characters.  Name field size is 100 Characters.

• All methods use POST method.

• All returns are in JSON format

• Attachments & Receipts are in stream format in the header record.

• Login Session binds to server API Address.

As of version 7.4 and up: 
Login and Authentication options
A. Login using 'login' method to get sessionId.

• As of Version 7.4 and up the direct login method requires two new parameters apiAuthCode and siteAuthCode. 

• apiAuthCode (API Hub username and password) - username:password <-- Please note this parameter must be base64 encoded

• siteAuthCode (Site username and password) -  username:password <-- Please note this parameter must be base64 encoded

• Please refer to the Postman Examples for a working example and note that any following API calls must include the sessionId (obtained from the login result array). 

B. API Key

• API Keys can now be generated here in API Hub by accessing Setup > Setup API Key. After key creation your applications can access API calls by passing the api-key:value pair via the request header. Please note that when using the API key the session is automatically handled and the sessionId parameter is not needed. Please refer to the Postman Examples for a API key working example.

C. Basic Authentication

• Basic Authentication can now be generated here in API Hub by accessing SETUP > Setup Basic Auth. After Basic Authentication credential creation your applications can access API calls by passing the Authentication key:value pair via the request header. Please note that when using the Basic Authentication the session is automatically handled and the sessionId parameter is not needed. Please refer to the Postman Examples for a working example of a request using basic authentication.