Implementation And Service
Tridata GmbH offers various server packages to equip suppliers and manufacturers with the velo.API interface. Depending on the range of functions you need, you can choose between three server variants.
Simplified Integration for Suppliers:
velo.API enables the connection of the platform backend via REST. This advancement promises a significant simplification of server programming from the supplier side. REST is an architectural style that facilitates communication between computers, providing a unified interface through standardized HTTP methods.
manufacturers/suppliers/brands, already using velo.API:
You will receive the access data directly from the respective manufacturer/supplier!
User of an ERP system from Tridata or HIW should use the velo.API link only!
velo.API: | https://gazelle.tri-data.de/ITriData.asmx/Veloapi |
Veloconnect: | https://gazelle.tri-data.de/ITriData.asmx/Connector |
Veloconnect 1.4: | https://gazelle.tri-data.de/ITriData.asmx/Veloconnect14 |
velo.API: | https://ghost.tri-data.de/ITriData.asmx/Veloapi |
Veloconnect: | https://ghost.tri-data.de/ITriData.asmx/Connector |
velo.API: | https://giant.tri-data.de/ITriData.asmx/Veloapi |
Veloconnect: | https://giant.tri-data.de/ITriData.asmx/Connector |
Veloconnect 1.4: | https://giant.tri-data.de/ITriData.asmx/Veloconnect14 |
velo.API: | https://ponbike.tri-data.de/ITriData.asmx/Veloapi |
Veloconnect: | https://ponbike.tri-data.de/ITriData.asmx/Connector |
Veloconnect 1.4: | https://ponbike.tri-data.de/ITriData.asmx/Veloconnect14 |
velo.API: | https://raleigh.tri-data.de/ITriData.asmx/Veloapi |
Veloconnect: | https://raleigh.tri-data.de/ITriData.asmx/Connector |
Veloconnect 1.4: | https://raleigh.tri-data.de/ITriData.asmx/Veloconnect14 |
velo.API: | Add-on for stock and sales data |
Veloconnect: | The server addresses are provided directly by Specialized |
Other suppliers are in preparation:
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
Veloconnect 1.4: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
Veloconnect 1.4: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
Veloconnect 1.4: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
Veloconnect 1.4: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
Veloconnect 1.4: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
Veloconnect 1.4: | The server addresses will be announced after going live |
velo.API: | The server addresses will be announced after going live |
Veloconnect: | The server addresses will be announced after going live |
+4 other suppliers who want to be named after going live.