There are some changes to the way access is granted and controlled to vendor applications using API-NG. The key changes are:
- 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 /wiki/spaces/7ccqm0ej51oaj0y7q8s664wo8/pages/2129931 section of the API-NG Reference Guide.
Sign up for subscription
A customer with an existing Betfair account visits vendorapp.com and wants to sign up for the vendor application. The customer then wants to purchase a 12 month subscription to vendorapp, so they purchase this from vendorapp.com. vendorapp.com then call the Account API-NG operation getApplicationSubscriptionToken, passing in their Application Key, a valid session token (to prove that they own that app key) and the length of the subscription required. Betfair return to the vendor a Subscription Token of the form ABCD-EFGH-IJKL. The subscription is then activated by calling activateApplicationSubscription token, passing in the subscription token and a valid session ID for the customer (in the header).
