The point of opening up the API is to allow products to be developed around it without any restrictions on shipping our code within the 3rd party application. That basically sums it up.
In order to receive data you need to have a data subscription and we pass through all exchange fees that exchanges charge depending on which particular pieces of data you would like to access. (We serve 350+ exchanges over this API)
Previously, the 3rd party app market was a bit restricted because app developers themselves couldn't necessarily bundle our SDK into their product due to the restrictive licensing and it was a hassle for the ecosystem of devs who write apps in this space. This makes it easier for them to build and ship products.
In order to become a data customer, you can either talk to a terminal with the SDK, or we sell a managed appliance that only serves the data. The SDK can talk to either without configuring it differently. All the rules on distributing the data apply no matter how you get it because the sources of the data (exchanges) are very, very restrictive about specific use cases of their data. The contracts spell out exactly who can place the numbers where and for what purpose. Basically, no matter who you get data from, displaying it publicly anywhere or distributing it as any part of service requires special legal contracts.
Thanks apaprocki for the clarification. Dont you think that an additional step would be have a public API directly accessible through internet? In the past customers had to buy dedicated lines for your service, then BLB gave the opportunity to use internet connections, but with desktop software or appliance inhouse. The next step will be giving direct access to api from the internet without other software involved (opening probably in this way more market for new web applications/services integration)
The point of opening up the API is to allow products to be developed around it without any restrictions on shipping our code within the 3rd party application. That basically sums it up.
In order to receive data you need to have a data subscription and we pass through all exchange fees that exchanges charge depending on which particular pieces of data you would like to access. (We serve 350+ exchanges over this API)
Previously, the 3rd party app market was a bit restricted because app developers themselves couldn't necessarily bundle our SDK into their product due to the restrictive licensing and it was a hassle for the ecosystem of devs who write apps in this space. This makes it easier for them to build and ship products.
In order to become a data customer, you can either talk to a terminal with the SDK, or we sell a managed appliance that only serves the data. The SDK can talk to either without configuring it differently. All the rules on distributing the data apply no matter how you get it because the sources of the data (exchanges) are very, very restrictive about specific use cases of their data. The contracts spell out exactly who can place the numbers where and for what purpose. Basically, no matter who you get data from, displaying it publicly anywhere or distributing it as any part of service requires special legal contracts.