Troubleshooting¶

Find the problem in the tables below. Each row gives the cause and the action. For all errors, see the Error catalog.

Access and signature¶

All these problems give the same response: HTTP 401 {"message": "Not Authorized", "code": 401, "result": "error"}.

Check	Action
Your code gives the URL of the worked example	Correct your code. See Sign a request
The parameters in the signature are sorted by name	Sort them. The order in the URL is not important
All parameters of the URL are in the signature	Add the missing parameters
The values in the signature are not URL-encoded	Use `+380…`, not `%2B380…`
`+` in the URL is encoded as `%2B`	Encode it. A `+` in a URL is a space
You encode the hexadecimal text of the hash with Base64	The text before `_` has 86 characters
The public key and the private key are of the same key pair, and the partner ID is correct	Use the values from your MEGOGO manager
The request comes from an IP address in the list	Send the request from a server in the list. After a change of your servers, send the new addresses to MEGOGO. See Operations

Problem	Cause	Action
A service ID from your manager is not in `subscriptions` without a phone number	The settings of the service	Tell your MEGOGO manager
`Service is not configured for this partner`	The service ID is not configured for your partner ID	Use a service ID from your MEGOGO manager
Code 40009	The subscription is not sold through partners	Tell your MEGOGO manager
Code 2006	The service ID is not a subscription	Use a subscription service ID

Problem	Cause	Action
`subscribe` gives code 2023	The subscription is already active, and the service has automatic renewal	No action is necessary
The end date did not change after `subscribe`	Code 2023: see the row above	No action is necessary
The end date moved one period forward after `resume`	There was no suspended subscription. `resume` worked as `subscribe`	Send `resume` only after your own `suspend`
After `resume`, the time that was left before `suspend` did not come back	You sent `subscribe` or `unsubscribe` while the subscription was suspended	Send only `resume` after `suspend`
After `unsubscribe`, the subscription is still in `subscriptions`	You used another service ID of the same MEGOGO subscription	Send `unsubscribe` with the service ID from `subscriptions`
The subscription is not in `subscriptions`, but the user had it	It is suspended, or it was stopped	Check your log of requests
The profile of the user shows an end date far in the future	The service has a long period with automatic renewal	No action is necessary. The subscription works until `unsubscribe`

Problem	Cause	Action
The user does not know how to watch	MEGOGO does not send messages about your subscription	Send the sign-in instructions to the user. See Activate a subscription
The user signed in, but does not see the subscription	The user signed in with another phone number, or the subscription is not active	Get `subscriptions` with the number of the user
A MEGOGO user was created for a wrong number	`subscribe` or `subscriptions` with this number	Check the number format on your side. To delete the user, tell MEGOGO support

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