Skip to end of metadata
  • Created by Former user, last modified by Former user on Dec 18, 2013
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

  • 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.

Sign up for subscription

  1. A customer with an existing Betfair account visits vendorapp.com and wants to sign up for the vendor application.  
  2. The customer wants to purchase a 12 month subscription to vendorapp, so they purchase this from vendorapp.com.
  3. 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.
  4. Betfair return to the vendor a Subscription Token of the form ABCD-EFGH-IJKL.
  5. The subscription token is then provided to the user (e.g. by e-mail) at registration.
  6. The subscription is then activated by calling activateApplicationSubscription token, passing in the subscription token and a valid session token for the customer (in the X-Authentication header).
  7. The activateApplicationSubscription service should be used in conjunction with the interactive login method.  See sample code here

 

 

 

  • No labels