The API login endpoint is the simplest method of integration for most applications in terms of development time expected to be required, but comes at the cost of being less flexible to edge cases than the embedded Betfair embedded login page. It will allow a user to provide a username and password or a username and (password + 2 factor auth code) if they have strong authentication enabled. Customers who writing bots are strongly recommended to use the non-interactive endpoint with an SSL certificate. We recommend that 3rd party applications which will be exposed to a wide range of users use the Interactive login method of embedding the Betfair embedded login page as this will allow your application to handle additional workflows, such as terms and conditions updates as well as additional jurisdictional specific identifiers.
The presence of the "Accept: application/json" will signal SSO that it should responde with JSON and not with a HTML page.
The username to be used for the login
The password to be used for the login. For strong auth customers, this should be their password with a 2 factor auth code appended to the password string.
Signals that the response should be returned as JSON
AppKey used by the customer to identify the product.