API List
- API Introduction
- Authentication Key API
- Server Date and Time
- Embed Image API
- Attachment Download API
- Common lookups API
CRM Integration API
- List of companies with basic details
- Complete details of a company
- List of customers of a branch with basic details
- Register Person
- Register company
- Register address
- Register contact query
- Login ID availability check
- Customer Login API
Delivery / Shipment Order API
Expense Claims Integration API
- Register Expense Claim
- Add expense item to claim
- Save and present claim for approval
- Get list of claims with basic details
- Get claim with all details
Inventory Module Integration API
Sales Module Integration API
- Register Quotation API
- Register Proforma Invoice API
- List of Commercial Invoices
- Number of Commercial Invoices
- Register Invoice API
Shopping Cart Integration API
- Price List API
- Create Shopping Cart Order
- Add product to shopping cart
- Update payment details
- Get order in shopping cart
- List of orders in shopping cart
Procurement Module API
Manufacturing Module API
Introduction
This document covers the API and instructions for integrating third party systems with Tuhund backbone. Tuhund offers secure and robust API access to deployments for a wide range for functionality and data. Access is controlled for every client and for every API. Access control is managed from respective Tuhund deployment.
The set of API namely "Tuhund third party system integration API," covered under this section, are all REST API delivered through servlet "apic" [protocol]://[domain]/apic/[API Name] and exchange data in JSON format. Options include wide range of filters like search, sort, organize, drill down level and so on.
For development environment, sandbox portal access, with complete functionality and realistic sample data, is available.
For both, development and production, environments separate authentication codes are provided to each vendor. Authentication code is use to generate Authentication key. Authentication key works on the same server from which the key was generated and expires every 24 hours by default. Life time of Authentication key can also be controlled from the respective deployment. Authentication key must be reused as long as possible to ensure best performance in terms of response time.
Every API has been given a distinct number called API Number, to make it simpler to refer to the correct API for support.
Instructions
Please click on the respective API in the left side navigation panel.
Please refer to Server Date and Time API to check possible errors that are common to all API. These errors are not repeated in other API pages.
