This is an old revision of the document!
Table of Contents
BI Direct
Introduction
BI Direct is an interface with a shared access point where each component can be selected separately. The fields of the interface components are “locked” and always identical across all databases. Development is carried out based on the shared solution principle. The interface can be activated and does not require any development work from Directo’s side. The necessary components must be agreed upon in advance. The interface is designed with BI (Business Intelligence) needs in mind and is suitable for use only with BI solutions.
API Key
To find the interface XML key and forward it to the developer:
Log in to Directo with a user who has SUPER rights
Open the employee card ‘XML’
Go to the Admin tab
Scroll to the section XML interfaces \
On the required interface row, click the button 
to view the key
Access to the Interface (URL)
Access to the interface is via the POST method, form/urlencoded, using the following URL: https://login.directo.ee/xmlcore/cap_bi/xmlcore.asp
Access requires a token. The token replaces both the appkey and the database name used in older interface types.
The token must be sent via POST as the variable TOKEN (similarly to an HTML form post) to the given URL to receive a response.
If the token is incorrect or sent improperly, the response will be <result type=„5“ desc=„Unauthorized“/> and if the variable TOKEN is missing, the response will be <err>token required</err>.
curl example
curl --location 'https://login.directo.ee/xmlcore/cap_bi/xmlcore.asp ' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'token=••••••' \ --data-urlencode 'get=1' \ --data-urlencode 'what=xxxxx' \ --data-urlencode 'ts=xx.xx.xxxx'
Pricing
The price depends on the selected components, with a 20% discount applied. Output of deleted documents is included free of charge.
Testing
BI Direct interface testing link: https://login.directo.ee/xmlcore/cap_bi/webupload.html
General
Output interfaces display all records — filtering can be done using query filters.
Each output may be requested up to 3 times per day!
Components
Selectable components
| Component (what) | Schema (XSD) | Filters |
|---|---|---|
| invoice | ws_arved.xsd | number, customercode, transactiondate, date1, date2, ts |
| receipt | ws_laekumised.xsd | number, date1, date2, ts |
| order | ws_tellimused.xsd | number, customercode, class, date1, date2, ts |
| customer | ws_kliendid.xsd | code, loyaltycard, regno, email, phone, closed, ts |
| purchase | ws_oarved.xsd | number, date1, date2, supplier, confirmed, status, ts |
| item | ws_artiklid.xsd | class, code, type, barcode, supplier, supplieritem, closed, ts |
| project | ws_projektid.xsd | code, customer, supplier, orderer, contract, closed, ts |
| stockreceipt | ws_sissetulekud.xsd | number, date1, date2, supplier, confirmed, ts |
| delivery | ws_lahetused.xsd | number, customer, type, status, ts |
| object | ws_objektid.xsd | code, master, type, level |
| user | ws_kasutajad.xsd | code, employee, internalcode, idnumber, closed, email, ts |
| supplier | ws_hankijad.xsd | code, regno, email, closed, ts |
| priceformularow | ws_hinnavalemid.xsd | code, item, class, ts |
| account | ws_kontod.xsd | code, closed, class |
| stocklevel | ws_laoseis.xsd | code, stock, ts |
| transactionrow | ws_kanderead.xsd | number, date1, date2, type, object, project, supplier, customer, rowdate1, rowdate2, ts |
| itemclass | ws_artikliklassid.xsd | code, master |
| delete | ws_kustutamised.xsd | number, code, document, ts |
| payment | ws_tasumised.xsd | number, date1, date2, reference, confirmed, ts |