- The introduction of Subscription Tokens, to provide a single identifier for a customer's subscription to an application.
- The use of Application Keys, which replace product and vendor software IDs to control API access.
- For details of the operations to manage subscriptions, please see the Accounts section of the API-NG Reference Guide.
Subscribing a New Customer
Preconditions: Customer has a Betfair account. Vendor has a Betfair vendor account, the app key for their app, and their (Vendor) session token.
- Customer visits Vendor’s web site and decides to sign up for the Vendor’s app.
- The Customer purchases a 12 month subscription to the application from the Vendor’s web site.
- 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).
- Betfair returns to the vendor a Subscription Token of the form ABCD-EFGH-IJKL.
- The Subscription Token is then provided to the instance of the Vendor’s app used by the Customer.
This may happen in a number of ways, including:
i) Emailed from Vendor to Customer, who then types it into the app.
ii) Associated with the Customer’s app instance by the Vendor, so that the token can be cited by the app based on Customer login to the app. - The Vendors App requires Customer to login to Betfair using interactive login method. See sample code interactive login sample code here.
- Betfair returns Customer’s session token to the app.
- The subscription is then activated by the app calling activateApplicationSubscription passing in the subscription token and a valid session token for the Customer