Development and SaaS Environment
Initially, the development will be done on a dedicated Vendor QA account. Once it passes Kaltura QA verification we will deploy the integration to the vendor's production account.
Both QA and SaaS environments will be available with the following interfaces:
| US | Ireland (EU) | Frankfurt (EU) |
API service | https://www.kaltura.com/api_v3/service/ | https://api.eu.kaltura.com/api_v3/service/ | https://api.de.kaltura.com/api_v3/service/ |
MediaSpace | <vendor account ID>.mediaspace.kaltura.com | <vendor account ID>.mediaspace.eu2.kaltura.com | <vendor account ID>.mediaspace.de2.kaltura.com |
MediaSpace admin | https://<client partnerID>.mediaspace.kaltura.com/admin/config/ | https://<clientpartnerID>.mediaspace.eu2.kaltura.com/admin/config/ | https://<clientpartnerID>.mediaspace.de2.kaltura.com/admin/config/ |
KMC | https://www.kaltura.com/index.php/kmcng | https://kmc.eu.kaltura.com/index.php/kmcng | https://kmc.de.kaltura.com/index.php/kmcng |
You can access the MediaSpace admin using your KMC credentials.
Setup
Kaltura REACH vendor account - A vendor who integrates with Kaltura will be provided with a dedicated Kaltura account (represented by a PID). This account will be configured accordingly by Kaltura to allow access to special REACH API services.
Client account - While developing the integration, another Kaltura account (represented by a PID) will be created for the vendor to allow the vendor to mimic a client issuing REACH tasks.
Supported Services CSV file - The vendor will fill in and provide the Supported Services CSV file. This CSV will contain the list of all supported services by the vendor (Catalog Items). While filling the CSV, the used values should match Kaltura's predefined enum values mentioned in the Kaltura Enums (Enums - Kaltura VPaaS API Documentation) related to REACH API section.
New types of services - For new types of services, a definition of the service input and output will need to be made. See examples in "Services input & output" section of the Integration Docs.
Kaltura validation / on-boarding process
The vendor will first do initial Quality Assurance on the QA environment. Once they decide that the integration is stable, Kaltura will also test on the QA environment. After the integration is verified by Kaltura, we will deploy the integration to Kaltura SaaS which means:
Kaltura will create a Vendor partner on SaaS.
Kaltura will create catalog items for the vendor services.
The vendor will start monitoring the tasks queue on SaaS using the SaaS domain.
