Skip to content

Activate many subscriptions

This guide shows how to activate MEGOGO subscriptions for many subscribers at one time, for example when you move your current subscribers to MEGOGO.

Before you start

  • The API does not have a request for many subscribers. Send one subscribe for each subscriber.
  • Each partner ID can send 1000 requests per minute. Above the limit, MEGOGO can return HTTP 429.
  • Each new subscription starts now and gets the full period of the service. You cannot set the start date or the end date.
  • We recommend that you tell your MEGOGO manager the date and the number of subscribers before you start.

Step 1. Prepare the list

  1. Make a list of the identifiers of the subscribers and the service ID for each subscriber.
  2. Remove the spaces at the start and at the end of each identifier. Use the same form of the identifier as in all your other requests.
  3. Remove the duplicate identifiers. Upper and lower case are the same subscriber.

Step 2. Send the requests

flowchart TD
    A[Next subscriber from the list] --> B[user/subscriptions]
    B --> C{Service is active?}
    C -- Yes --> E[Write: already active]
    C -- No --> D[subscribe]
    D --> F{Result}
    F -- successful: true --> G[Write: activated]
    F -- Code 2023 --> E
    F -- Other error --> H[Write: error, check later]
    F -- Timeout or 5xx --> B
    E --> L[user/changeCredentials if the subscriber has no login]
    G --> L
    L --> A
    H --> A

For each subscriber:

  1. Get user/subscriptions. If the service is already active, do not send subscribe: in the mode "renewal by the partner", it adds one more period. User not found means that the subscriber has no subscription.
  2. Send subscribe.
  3. If the subscriber has no MEGOGO login, send user/changeCredentials. See Activate a subscription.
  4. Write the result for the subscriber in your system.

Each subscriber needs up to three requests. Keep the speed below the limit, so that your other requests also get through: for example, 250 subscribers per minute (750 requests). If you get HTTP 429, wait 1 minute and continue.

WARNING

After a timeout or an HTTP 5xx response, start again from step 1 for this subscriber. See Retries.

Step 3. Check the result

  1. For the subscribers with an error, find the cause in the Error catalog and send the requests again.
  2. For some subscribers, get user/subscriptions again and make sure that the service is active.

Step 4. Tell the subscribers

MEGOGO does not send a message to the subscribers. Show the login and the password in the personal account of each subscriber. See Activate a subscription.

Guide version 1.0.2, 2026-11-08 · Report a problem on this page