Skip to content

Go-live checklist

Do these checks before you open the MEGOGO content to your users. Each item has a link to the page that describes it.

Credentials and access

  • You have the production partner ID, the keys for each platform, the salt and the service IDs. See Credentials.
  • The private keys and the salt are only on your servers. The client applications do not contain them. See Security.
  • MEGOGO added the IP addresses of your production servers to the list of the production partner ID. See Credentials.
  • Each platform of your service uses its own key. See Platforms and rights.

Catalog

  • Your server downloads the production XML feed one time each day, after 05:00 UTC, and keeps the previous catalog if the new feed is not ready. See Build and update the catalog.
  • The catalog shows only the objects that your keys can play: the platform flags, DRM and 4K settings. See Build and update the catalog.
  • The images use the sizes from Images.
  • Each request to the Content API has lang.
  • Your applications show that MEGOGO supplies the content. See Content attribution.

Billing

  • You send subscribe only after a successful payment, and you bill the user only after "successful": true. See Sell a subscription.
  • You know the renewal mode of each service, and your system follows it. See Sell a subscription.
  • When a subscription ends in your system, you send unsubscribe.
  • For TVOD and DTO, you use tariff_id from /video/info, not the prices of the XML feed. See Sell a single title.
  • Your system compares its data with user/subscriptions regularly. See Subscription lifecycle.
  • Before you retry subscribe or buyMovie, your system checks user/subscriptions. See Retries.
  • Your system reads the error code at the end of message, not the text. See Error catalog.

Authorization and playback

  • You use the same user identifier in the Billing API and in /auth/by_partners. See Authorize a user.
  • Your server keeps the access token until it expires and gets a new one with /auth/refresh.
  • Before you request a stream of an AdVOD or FVOD video, your system makes sure that the user has your subscription. See Sell a subscription.
  • You send /stream only when the user starts the playback, and you do not keep src in a cache. See Play a video.
  • Your players play the stream_type and drm_type of each key. You tested a video with DRM on each platform that has DRM. See DRM.
  • When src is empty, your application shows a message for each restriction code. See Error catalog.
  • The audio tracks in the player are only the tracks of audio_tracks. See Change playback settings.

Operations

  • Your system stays below the request limits, and it uses a cache for /configuration and the lists. See Limits and Cache.
  • Your logs have all Billing API requests and responses with the time (UTC), and they do not have keys, tokens or src URLs. See Logs.
  • Your team knows the support address: supportpartners@megogo.net.

Last test on production

Do the full path with the production credentials and one test user identifier:

  1. subscribe for the user.
  2. /auth/by_partners for the user.
  3. /stream of a video from your catalog on each platform. The video plays.
  4. unsubscribe for the user. user/subscriptions does not show the subscription.

The tutorial shows these steps with the test credentials.

Guide version 1.4.1, 2026-10-31 · Report a problem on this page