Free API

[gus]

On bnl's post, as I said the procedure for Vendors, whilst retaining the account/appKey/SSOID relatiship, is different, and quite a bit more complicated. It's decribed here:

https://api.developer.betfair.com/se...ices+in+API-NG

[bnl]

Nope, that's not how it works.
The developer appKey that you create via the visualiser IS linked to your Betfair account
...
that's why you have to provide a Session Cookie (SSOID) when you are creating an appKey.
...
So you can create any number of apps,
so long as they all use the same developer appKey that you
created in the Visualiser, but they can only be used on the account
that the appKey was created on, unless you change the appKey (in the code, as above).

So if this is _how it works_ then
1 - why is it called AppKey ? And not AccountKey?
2 - why does it indeed work to have a bot running on several Accounts
in parallel with the AppKey Hardcoded into the app?

As I said, I've got THE SAME EXECUTABLES running ON THE SAME MACHINE
with DIFFERENT ACCOUNTS. No problem.

Because the AppKey and the Account used to log in is all that is needed.
Then you get a ssoid, and from that moment on,
the SAME AppKey with an unique ssoid is all that is needed
to trace you back to the account. The ssoid alone is really enough for that,
the AppKey states the App. Not the account.

/Björn

[bnl]

On bnl's post, as I said the procedure for Vendors, whilst retaining the account/appKey/SSOID relatiship, is different, and quite a bit more complicated. It's decribed here:

https://api.developer.betfair.com/se...ices+in+API-NG

and step 3 states

The Vendor’s web site server then calls the Account API-NG operation getApplicationSubscriptionToken, passing in the Vendor’s app key, a valid session token for the Vendor’s Betfair account (to prove that they own that App Key) and the length of the subscription required (365 days in this scenario).

That is, the vendor does not re-apply for a new AppKey
for each new customer account

/Björn

[gus]

You can use the app on two different accounts because the accounts are both yours, so you know the Usernames and Passwords, but if you wanted to make your app available to someone else then they wouldn't be able to use it (unless they knew your Username and Password, and were therefore using it on your account).

[bnl]

Unless the bot reads account info from a file
or provides a login screen...

I read from file, and trust the os to not reveal it anyone else.

I do run several accounts like this on one machine.
But the account owners could run their own set of processes,
on their own machine, with their username/password.

Still, it is the same AppKey, since it is the same bot ...
/Björn

[gus]

Yes, I don't think we're in disagreement on this.

Firstly, i think we have to distinguish betweeen 'developer' Apps and 'vendor' Apps.

So, in discussing 'developer' Apps:

the developer AppKey is linked to the application, but it is also linked to the account.

For example if I gave one of my own Apps to someone else, they wouldn't be able to use it because, although they would be able to log-in to Betfair with it using their BF credentials, API_NG would refuse it access using the SSOID created by their log-in because their account would not be associated with the 'embedded' appKey.

The only way I could let someone use my App would be for them to generate their own appKey (via the visualiser), and for me to substitue their appKey for my appKey.

Effectively it would be a new application.

If I want to allow others to use to use my App without changing the appKey, the only way I can do this is by obtaining Vendor certification from BF.

Then I can use the Vendor Account API, and using that I can (idirectly) grant other people's accounts permission to access the api using my appKey as described at: https://api.developer.betfair.com/se...ices+in+API-NG

[bnl]

Yes, I don't think we're in disagreement on this.

the developer AppKey is linked to the application, but it is also linked to the account.

I'm sorry but I do disagree here

For example if I gave one of my own Apps to someone else, they wouldn't be able to use it

Wrong, this is exactly what I do

because, although they would be able to log-in to Betfair with it using their BF credentials, API_NG would refuse it access using the SSOID created by their log-in because their account would not be associated with the 'embedded' appKey.

Hmm, yes perhaps, but why would the application
use my ssoid, when it is running under my friends account ?

The only way I could let someone use my App would be for them to generate their own appKey (via the visualiser), and for me to substitue their appKey for my appKey.

Wrong.

Somehow I think I have not been clear enough.
For simplicty say that I have 1 bot.
That is one (1) executable file into which I have
compiled the AppKey for this bot.

Upon start on my machine, it reads user/pwd from a file, say login.ini.

It logs in (using the interactive method)
and retrives a ssoid.

It can now interact with Betfair, ask for markets and
do betting stuff. In my account.

Now, my friend, who has a copy of this binary, also starts
the bot. It reads MY FRIEND'S login.ini and logs in to
Betfair, using his account. But STILL the same hardcoded AppKey

His bot will now get ANOTHER ssoid, and can, just as mine,
interact with betfair.

Effectively it would be a new application.

No, it would not. It is THE SAME EXECUTABLE
RUNNING DIFFERENT ACCOUNTS.

If I want to allow others to use to use my App without changing the appKey, the only way I can do this is by obtaining Vendor certification from BF.

No.

Then I can use the Vendor Account API, and using that I can (idirectly) grant other people's accounts permission to access the api using my appKey as described at: https://api.developer.betfair.com/se...ices+in+API-NG

Yes indeed, but that is something different

I'm sorry if I have been unclear, but I've been running
my own, and a friends account like this since API-ng started up.

At first I logged in via API6, but the same thing there,
get the ssoid and be happy. It does run with the same AppKey
with different betfair accounts. It really does .
/Björn

[BetfairDeveloperProgram]

App Key Rules & Configuration

Hi,

I'd just like to clarify how App Keys are configured from Betfair's perspective:

• When first created via createDeveloperAppKeys both the delayed and live App Keys are associated with a single Betfair account only
• Users with more than one Betfair account must create a new App Key for each account.
• App Keys require an account to be subscribed to them by default.
• If an account isn't subscribed to an App Key and attempts to make a request to API-NG, the error INVALID_APP_KEY will be returned
• Only licensed vendors can use the Vendor Services API to subscribe additional customers to use their App Key (Application).

@bnl - please contact BDP@betfair.com if you are experiencing different behavior from that described above and we'll investigate further.

Thanks

Neil

[bnl]

Hi,
@bnl - please contact BDP@betfair.com if you are experiencing different behavior from that described above and we'll investigate further.

And suddenly I feel so stupid.
As writing a mail to bdp, and giving examples,
I discover that the bot also reads the AppKey from a file.

So it does turn out that I am wrong.
And that the accounts actually uses one AppKey per account.

My apologies to all of you that tried to convince me that I was wrong.

@Neil: since I was wrong, there won't be a mail from me regarding this topic.

/Björn