The Vendor Program. Helping your App reach Betfair customers

  • NEW! Build web-applications! Enable Betfair Exchange betting on your website.
  • Use the API to create betting apps and distribute these to Betfair customers
  • Get certified and promote in the Betfair App Directory
  • Use the Vendor Services API to manage user subscriptions and monetise your App

THE PROCESS FROM START TO FINISH

As you might imagine, the process of creating a betting App for distribution to Betfair customers needs to be stringent.

Here's an overview of the process:

  1. 1 Sign up for the vendor program

    This tells us who you are and what your intentions are, so that we can license you correctly. Please indicate whether you are intending to develop a desktop, web or mobile (browser extension Apps are not permitted) application or if you'd like to apply for a Historical Data licence.  Any application that you develop should enable end users to place bets into the Betfair Exchange via the Betfair API.

    Please note:  Your Betfair account must be verified before your application will be considered.  We do not accept Software Vendor licence applications from any country where Betfair account registration is not permitted.

  2. 2 Develop your App

    Once you're signed up and approved, you can start development. There are some important things you need to consider before you start coding:

  • If you’re building a web app you must utilise the Vendor Web API to manage end user interactions with the API.
  • A one off licence fee of £499 is payable when you submit your application for security certification.

 

  1. A Application Security Certification
    Broadly speaking, we need to ensure that customers can use their accounts in a secure fashion, without the possibility of hijacking, misuse, or any form of malicious activity. This requires you to develop your App with the Security Authorisation Checklist in mind.
  2. B Product Requirements

    In addition to the security measures, additional technical and commercial product requirements also apply. Requirements include compliance with the Gambling Commission standards, data request management and specific licensing requirements for certain countries. This requires you to develop with the Product Authorisation Checklist in mind
  3. C User Provisioning 

    Provisioning a user to an application must follow the correct workflow as shown in the Vendor Service API documentation.

     

  1. 3 Submit your app

    Once you're ready, the submission process will guide you through submitting and complying with:

    1. A Application Security Certification
    2. B Product Requirements
    3. C User Provisioning

    SECURITY CHECKLIST

    Your application may not communicate with the API through a proxy of any description. All communications must be directly with the API and must be over a secure channel.
    You must not have visibility of a user's Betfair username, password or any other sensitive data that may link a user of a product to a Betfair account.
    An application must communicate directly with Betfair via the API to validate a customer.
    An application must never store or log the user's Betfair password.
    An application must not store or log the username in plain text.  If the user has chosen to store their username locally (by performing an explicit action to indicate their wish to do so) it should be encrypted (AES with minimum 128 bits key length).
    An application must display an agree/disagree model dialog to the user when the user indicates a desire to store their username locally. The default action of the dialog should be to not save the username.
    An application may not implement automatic login as this would require the application storing the password locally.
    The application must provide a 'Logout' function
    An application must use the Vendor-registered user ID (not the Betfair username) credentials to validate subscription, fetch news and update the application and all other Vendor/application specific communication.
    The provisioning (where applicable) of the account to use the application with the Betfair API must be via the Vendor Services API or Vendor Console - see Part II

    Application Details

    Version
    Application type
    Product overview and outline of functionality
    URL to download test client
    Details of encryption
    Session management and username/password handling
    Source code of logon and session management

    Gambling Commission Requirements

    Confirmation that you have read and adhered to the Gambling Commission Requirements?

    Product Authorisation Checklist

    You understand that your application should not make any more than five market prices requests, per market in any one second.
    the application includes a link to the Betfair Charges page for customer reference
    The application requests gZipped responses from the API
    The application supports forced updates to customers
    the application does not make any more than five market prices requests, per market in any one second
    The application does not reveal the assigned Application Key to users

    Product Authorisation submission

    A user manual or comprehensive list of features is supplied.
    A versioning URL that can be used by the application and Betfair is provided
    Breakdown of the calls your application makes (default settings and maximum requests per second)
    If you are releasing a new version of an application, you will need to submit a breakdown of the calls comparing the current version with the new version to be released.
    You have read the Advertising and Marketing Guidelines in relation to any promotional material including your product website.
    Any other information?

     

  2. 4 Once approved, list your App in the App Directory

    Please submit details of your application using the form below. This will be reviewed by the BDP team and uploaded once approved:

    Platforms supported