Operations¶

This page gives the rules for the daily work of your integration: limits, retries, logs and changes of your servers.

Limits¶

Each partner ID can send 1000 requests per minute. Above the limit, MEGOGO can return HTTP 429 Too Many Requests.

Do not send subscriptions for all users on a schedule. Send it only for the users with a change.
To increase the limit, ask your MEGOGO manager.

Retries¶

Send a request again only after a timeout or an HTTP 5xx response.

Get subscriptions for the user. Make sure that the first request did not change the subscription.
If the first request did not change the subscription, send it again.
Wait 1 minute between the attempts. Make a maximum of 6 attempts.

WARNING

subscribe and resume are not idempotent. A second successful request can add one more period. Always do step 1 before you send them again.

You can send unsubscribe again without the check: for a subscription that is not active, it changes nothing.

Logs¶

We recommend that you keep a log of all requests and responses, with the time in UTC. Give the time of the request and the response to MEGOGO support.

WARNING

Do not write the private key to the logs. Keep the phone numbers in the logs as your data protection rules require.

Changes of your servers¶

MEGOGO accepts the requests only from the IP addresses of your list.

WARNING

Before the IP addresses of your servers change, send the new addresses to supportpartners@megogo.net with your partner ID. Requests from an address that is not in the list get HTTP 401.

Support¶

Send an e-mail to supportpartners@megogo.net. Write:

your partner ID;
the request (without sign) and the response;
the time of the request in UTC.

Guide version 1.0.0, 2026-11-02 · Report a problem on this page