Skip to content

Error catalog

This page lists all responses with an error. Each row gives the cause and the action.

How to read an error

Response Format
Result of a request HTTP 200, {"successful": false, "message": "..."}
Format error HTTP 400, {"message": "Invalid request format", "code": 400, "result": "error"}
Access error HTTP 401, plain text: Partner {partner_id} not found (ip /{address})

If message ends with code and a number, use the number. Do not use the rest of the text: it can change.

{"successful": false, "message": "Exception while trying to buy object, code 2023"}

Codes in message

Code Request Cause Action
2006 subscription/{operation} The service ID is not a subscription Use a subscription service ID from your MEGOGO manager
2009 subscription/{operation} The subscription is not for sale Tell your MEGOGO manager
2010 subscription/{operation} The subscription is not found Tell your MEGOGO manager
2012 subscription/{operation} The settings of the subscription are not correct Tell your MEGOGO manager
2013 subscription/{operation} The subscription is not available in the region Tell your MEGOGO manager
2016 subscription/{operation} MEGOGO cannot create the service of the subscriber Retry later. If the error stays, tell MEGOGO support
2023 subscribe, resume The subscription is already active, and the service does not permit a renewal of an active subscription. Or the end date would be more than 15 years from now No action is necessary
40000 All The identifier is empty or has more than 254 characters (ISDN must be non-empty, ISDN must be less 255 symbols). Or the operation is not known (Invalid operation passed) Correct the request
40009 subscription/{operation} The subscription is not sold through partners Tell your MEGOGO manager
40416 subscription/{operation} The service ID is not configured for your partner ID Use a service ID from your MEGOGO manager

Messages without a code

message Request Cause Action
User not found user/subscriptions MEGOGO has no subscriber with this identifier No subscriptions. Check the identifier
Other users already have this email user/changeCredentials Another MEGOGO user has this login. Upper and lower case are the same Make a different login
Invalid password user/changeCredentials The password has fewer than 6 characters Make a longer password
Parameter password should not be empty or null user/changeCredentials No password in the request Add the password
User {identifier} not found for partner {partner_id} user/changeLogin MEGOGO has no subscriber with the old identifier Check the identifier
Text with Duplicate entry user/changeLogin MEGOGO already has a subscriber with the new identifier Tell MEGOGO support
ISDNs must be different user/changeLogin The old and the new identifiers are the same No action is necessary

HTTP errors

HTTP status Body Cause Action
400 {"message": "Invalid request format", "code": 400, "result": "error"} A required parameter is not in the request Add the parameter
401 Partner {partner_id} not found (ip /{address}) The partner ID is not known, or the IP address is not in the list of your partner ID See Troubleshooting
404 {"result": "error", "message": "Invalid request format", ...} The path is not correct Correct the URL
406 Empty The HTTP method is not correct, for example POST for user/innerId or GET for user/changeCredentials Use the method of the API reference
429 — More than 1000 requests per minute for your partner ID Send fewer requests
5xx, timeout — Temporary problem See Retries

Successful responses that need attention

Response Meaning
unsubscribe or suspend: "successful": true Also when the subscription is not active. Use user/subscriptions to check the state
resume: "successful": true without a suspended subscription resume worked as subscribe: it added a period or started a subscription
user/changeCredentials: "successful": true with a login that is not an e-mail address MEGOGO does not check the format. Check it yourself
user/innerId: no email The subscriber has no login. See Activate a subscription

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