Account

DEPRECATED: see GET /v3/accounts

get

DEPRECATED: see GET /v3/accounts

Accounts

Creates a new account within the custom billing vendor. This will fail if the end user already has an account.

post

Creates a new user account within the custom billing vendor. Optionally, the user can enter their payment method. They can then purchase any product that does not require a special payment method, such as a promo code or earned credits. Later the user can update their payment method. This POST fails if the end user already has an account.

get

Returns fields associated with an account.

Creates a new payment method or returns all the registered payment methods.

post

Creates a new payment method for the current account. To do this, you register a tracking ID that is used to pay using the payment method type. Valid types of payment are credit card and PayPal. When the tracking ID has been paid, it can be reused to create a new subscription or one-time charge.

get

Returns all the payment methods previously registered for the current account.

Initialize payment method registration to setup the tracking ID.

post

Creates a new token that is used to register a new payment method. This token identifies the payment method in other eCommerce operations. This token is not the same as an Ooyala Account Token, see Security Schemes.

WORKFLOW

Creating a new payment method is a three-step process. NOTE: Depending of the billing vendor this flow may have less steps.

For Credit Card:

  • 1. To Register a Payment Method: Initialize payment method registration to setup the tracking ID (after this, user submits confidential data).
    POST /v3/accounts/payment-methods/token
  • 2. Enable user to submit credit card information to billing vendor.
  • 3. To Confirm a Payment Method:
    POST /v3/accounts/payment-methods
    Creates a new payment method for the current account. Valid types of payment are credit card and PayPal.

For PayPal:

  • Same steps as before; however, at step two, the user will be redirected to a PayPal URL where they will enter their PayPal credentials, review the payment, and approve it. If the submission succeeds, the user will be redirected to the “success_callback” that you have specified, and should trigger the confirm step. If there’s a problem from PayPal, the user will be redirected to “error_callback” that you have specified.

Helps to pay an invoice of a subscription used by the payment method “MAP”.

put

The invoice ID to identify the invoice to pay for a subscription. The invoice ID is used by the payment method “MAP”.

Subscription associated with an account.

post

This route creates a subscription for the current user.

get

This route returns all the subscriptions associated with the current user.

Creates a new subscription or remove or update a specific subscription of the current user previously created.

put

Helps confirm the payment of a subscription by a hosted page.

get

Returns a specific subscription for the current user.

delete

Changes the status of a specific subscription for the current user to canceled. Cancellation prevents further renewals. The user’s entitlements remain until the end of the current cycle.

Creates an one time charge or returns all the one time charges associated at the current account.

post

Creates a one-time charge used for Pay-Per-View products.

 The hash field in the request must be formed as is shown below.

 Create a string with the format:

  base64 ( SHA_256( [Assets] + [Labels] + [Offers] , KEY) )
  
 Where:

  [Assets] = Asset_1 + Asset_2 + ... + Asset_n
  [Labels] = Label_1 + Label_2 + ... + Label_n
  [Offers] = Offer_1 + Offer_2 + ... + Offer_n
  
Each of thease element has this format:

  ContentId + ExternalProductID + startTime + endTime + rentalWindow.
  KEY = backlot API key.
  

get

Returns the history of one-time charges on the current account.