mikeholczer Posted February 14, 2015 Report Share Posted February 14, 2015 From what I have been able to piece together from reading various posts, in order to use the API, one needs to configure their btsync app to include their api key for the value of a "api_key" property in the "web_ui" section of the config file. This seems like an odd implementation of an API key. It seems like what it actually does is enable the API "mode" of btsync rather than authenticate a API client as being from a "trusted" developer. If I am going to work on an integration with the btsync API, I would want any btsync user to be able to take advantage of it, but just ones that unlock the API mode of the app by registering as a developer. Am I missing something? Or is this API Key process just something that is required while the system is in beta? Quote Link to comment Share on other sites More sharing options...
Bowler Hat Posted March 19, 2015 Report Share Posted March 19, 2015 I'm thinking that it will eventually become an identifying key in the way that other cloud systems have them. But right now I suspect its a case of controlling who is experimenting with the API. Until there is more documentation and the API is more complete and tested I guess BT doesn't want to spend all its time answering basic questions. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.