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!

Bike & Co
velo.API:https://bico.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://bico.veloapi.net/ITriData.asmx/Connector
velo.API:https://bike24.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://bike24.tri-data.de/ITriData.asmx/Connector
velo.API:https://cannondale.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://cannondale.veloapi.net/ITriData.asmx/Connector
Veloconnect 1.4: https://cannondale.veloapi.net/ITriData.asmx/Veloconnect14
Cervelo_Logo_Red
velo.API:https://cervelo.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://cervelo.tri-data.de/ITriData.asmx/Connector
Veloconnect 1.4:https://cervelo.tri-data.de/ITriData.asmx/Veloconnect14
velo.API:https://cratoni.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://cratoni.tri-data.de/ITriData.asmx/Connector
velo.API:https://cycleunion.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://cycleunion.veloapi.net/ITriData.asmx/Connector
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
(nur Stammdaten)
velo.API:https://haberland.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://haberland.tri-data.de/ITriData.asmx/Connector
Giant_Logo
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
Kalkhoff Logo
velo.API:https://kalkhoff.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://kalkhoff.veloapi.net/ITriData.asmx/Connector
Veloconnect 1.4: https://kalkhoff.veloapi.net/ITriData.asmx/Veloconnect14
velo.API:https://messingschlager.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://messingschlager.veloapi.net/ITriData.asmx/Connector
velo.API:https://nc17.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://nc17.veloapi.net/ITriData.asmx/Connector
velo.API:https://nusshold.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://nusshold.tri-data.de/ITriData.asmx/Connector
Pierer Logo
velo.API:https://pexco.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://pexco.tri-data.de/ITriData.asmx/Connector
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:https://saarrad.veloapi.net/ITriData.asmx/Veloapi
Veloconnect: https://saarrad.veloapi.net/ITriData.asmx/Connector
velo.API:https://scott.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://scott.tri-data.de/ITriData.asmx/Connector
velo.API:Add-on for stock and sales data
Veloconnect: The server addresses are provided directly by Specialized
velo.API:https://stevens.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://stevens.tri-data.de/ITriData.asmx/Connector
TDCC
velo.API:https://dataclearingcenter.tri-data.de/ITriData.asmx/Veloapi
Veloconnect: https://dataclearingcenter.tri-data.de/ITriData.asmx/Connector
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.

how can you implement velo.API?

All circumstances and your ideas will be discussed in a personal meeting. This will determine which velo.API server variant suits best for you. You can arrange a consultation here.

arrange a consultation

All circumstances and your ideas will be discussed in a personal meeting. This will determine which velo.API server variant suits best for you. You can arrange a consultation here.

We set up a test server for you and you will have access to the extensive documentation of the velo.API server. This is followed by a technical briefing.

we will provide you with a TESTSERVER

We set up a test server for you and you will have access to the extensive documentation of the velo.API server. This is followed by a technical briefing.

You can upload your data to the server via a XML/Soap interface. We check the data and after approval we set up the live server.

Transfer your data to the server

You can upload your data to the server via a XML/Soap interface. We check the data and after approval we set up the live server.

Before the test server goes live, we recommend a test phase with a few selected customers.

Test phase with customers

Before the test server goes live, we recommend a test phase with a few selected customers.

After a successful test phase, the go-live takes place. You and your dealers can now use all velo.API functions. Inform your dealers about the velo.API interface and what advantages they will benefit from.

GO-LIVE of your velo.API Server

After a successful test phase, the go-live takes place. You and your dealers can now use all velo.API functions. Inform your dealers about the velo.API interface and what advantages they will benefit from.

Arrange a consultation now