This release is now live!
This release includes the following functionality:
Account Operations (Vendor API)
- A new operation getVendorClientID that returns a unique VendorClientId for a customer to the vendor . This operation creates a VendorClientId if one does not already exist.
- Updated operation activateApplicationSubscription that now generates a new VendorClientId if one does not exist when activating a subscription.
- Updated operation listApplicationSubscriptions which now returns a VendorClientId for active subscriptions.
- A new operation getApplicationSubscriptionHistory that returns a list of all subscriptions that are associated to a customer’s VendorClientId.
- Vendors are now able to attach some information about a customer to a subscription via a new attribute called external_ref. This reference could be a previous subscription reference or an old vendor client id used in API-6, for example.
- Vendors can pass in the external_ref in an updated getApplicationSubscriptionToken operation.
- Vendors can retrieve the external_ref via an updated listApplicationSubscriptionTokens operation and via the new getApplicationSubscrption operation.
Deployment of API-NG to Australia
The new API is now deployed in Australia. This is currently deployed dark and will be non-dark after LBR has been deployed to Australia and we have full compliance sign off, both expected tomorrow.
Bets Now Ordered by Matched Date
API customers were able to have bets ordered by matched date/time on API-6 and in an effort to achieve parity the listCurrentOrders operation on API-NG now offers this same functionality.