Introduction

The AminoTV API currently has three authentication schemes:

Name	Purpose	Persistence	Auth Mechanism
Management API	To protect the endpoints that customer BSS integration uses	N/A	IP restriction
Client API	General purpose API calls made by clients on behalf of users	Cookie persisted server session	HTTP Digest
Service	A layer of security that identifies the client itself	Cookie persisted server session	HTTP Digest

Example client implementations

Java

Our upcoming AndroidTV SDK has support for logging in and managing service authentication.

Sample Java code

sdk.user().login("userName", "password")
    .subscribeOn(Schedulers.io())
    .observeOn(AndroidSchedulers.mainThread())
    .subscribe(
        response -> Toast.makeText(this, "Login successful", Toast.LENGTH_LONG).show(),
        t -> Log.e(TAG, "Failed to login", t)));

Javascript

The official AminoTV SDK has support for logging in and managing service authentication.

Please see the documentation at https://hybridteam.aminocom.com/sdk/api/modules/user/login

Sample Javascript code

sdk.user.login('me@example.com', '12345678')
  .then(() => {
    // Login successful
  })
  .catch(error => {
    // Login failed
  });

Getting a cookie for manual testing with Postman or similar

Use your web-browser to log in normally.
Use the developer inspect tools to look at the headers sent to an API call.
Copy the cookie that your browser sends (see image)
Include that header in your test request too

Authentication

Introduction

Example client implementations

Java

Javascript

Getting a cookie for manual testing with Postman or similar