This page describes all the errors returned by MeaningCloud's public APIs. For each error there's a description of what's happening, and some tips to resolve it.

What does it mean?

The license key you are sending to use the API is not correct or it's not authorized to make requests to the API in question.

How do I fix it?

The first thing you have to do is to check that the key your are sending is your license key. Sometimes it's common to add a blank space at the beginning or at the end when copying and pasting it, or even to remove a character accidentally.

Another possibility is that you are not using MeaningCloud in compliance with our terms and conditions and you have been banned from using the service. In these cases we will inform you in the developer's home. If you have been banned and it's a mistake, do write us to support@meaningcloud.com and we will fix it as soon as possible.

APIs it applies to

101: License expired

What does it mean?

The license key you are sending to use the API has expired.

How do I fix it?

Send us an email support@meaningcloud.com and we will check if it is an issue with the license or inform you about the possible alternatives.

APIs it applies to

102: Credits per subscription exceeded

What does it mean?

Each plan has a maximum number of monthly credits associated to it. This error is returned when you have run out of credits for the current month.

How do I fix it?

There are two possible solutions: either to wait for the credits to be reset when your billing month ends (you can check the date in your license information), or to upgrade your plan to have a higher volume.

Aside from the free plan, we provide four different paying plans to cover those scenarios in which the requirements are more demanding. In order to buy any of the paying plans, you just need to click on upgrade, where you will be able to add the billing data and then proceed to subscribe the plan you want.

APIs it applies to

103: Request too large

What does it mean?

Every API has a limit on the number of words that can be analyzed in a single request, much like the size limit operations such as POST have. In our case, we use words as the way to measure this limit, so there's less of a dependency on the format used to process the text.

All of our APIs are currently limited to 50000 words except for Text Clustering, which lets you process up to 100000 words in a single request.

How do I fix it?

Currently the only option is to divide the text you want to analyze into several requests that do not surpass the limit.

APIs it applies to

104: Request rate limit exceeded

What does it mean?

This error is returned when you've gone over the limit set by your plan for the number of requests you can carry out concurrently, more specifically, per second.

How do I fix it?

If you are sending the requests sequentially and you are getting this error, a solution is to establish a throttle (pause) between calls, ensuring they proceed below your plan rate limits.

If you require a higher rate limit, check our plans and pricing, or just write us with your requirements to work out a solution.

APIs it applies to

105: Resource access denied

What does it mean?

This error is returned when you don't have access to a resource or language, either because you are not subscribed to any of the packs that include it or because the trial period has finished.

How do I fix it?

You can check to which pack the resource belongs in the vertical or language packs sections, and then in your subscription, check if you have access to that pack.

If you require access to the resource/s included in a pack, check our plans and pricing to subscribe to it, or just write us with your requirements to work out a solution.

APIs it applies to

200: Missing required parameter(s): name of the parameter

What does it mean?

This error is returned when you have made a request to an API and you have not specified one of the required parameters. The parameter missing will be specified in the error message.

How do I fix it?

You need to add the parameter indicated in the error to the request you are making to the API. You can check which parameters are requiered in the request section of the documentation associated to the API you are using.

APIs it applies to

201: Resource not supported

What does it mean?

This error is returned when you have sent an incorrect value for the model or ud parameters.

How do I fix it?

Check that the value you are sending is one of the supported values for the API you are using. You can find detailed information in the request section of the API documentation.

APIs it applies to

202: Engine internal error

What does it mean?

An internal error has occurred in our engines.

How do I fix it?

Wait a few minutes and try again. If the issue persists, send it to us through our support form, so we can solve the issue as soon as possible.

APIs it applies to

203: Cannot connect to service

What does it mean?

The service is not able to serve the request you have made.

How do I fix it?

This issue is generally related to high load in our severs, so it's usually enough to wait a few minutes and try again. If the issue persists, send it to us through our support form, so we can solve the issue as soon as possible.

APIs it applies to

204: Resource not compatible for the language automatically identified for the text

What does it mean?

Resources are defined for a particular language. This error is returned when the language automatically detected when using lang=auto does not match a resource among the ones specified in the ud or model parameters.

How do I fix it?

You can check that you are using the correct value in the model parameter. If you are obtaining this error frequently in your analyses, a way to avoid it is to specify the language yourself instead of having it automatically detected.

APIs it applies to

205: Language not supported

What does it mean?

This error is returned when you have sent an incorrect value for the lang parameter.

How do I fix it?

Check that the value you are sending is one of the supported values for the API you are using. You can find detailed information in the request section of the API documentation.

APIs it applies to

206: Number of IDs does not match number of texts

What does it mean?

This error is returned when you have sent in the Text Clustering API a different number of texts (txt) and IDs (id). Each ID sent has to correspond to one of the texts, so if the number is different, this error is returned.

How do I fix it?

Check that you are sending the same number of elements in both the txt and id parameters. Each element is specified in a new line, so it's always useful to check if the same number of lines are being sent and if the lines are correctly delimited.

APIs it applies to

207: Mode not supported

What does it mean?

This error is returned when you have sent an incorrect value for the mode parameter.

How do I fix it?

Check that the value you are sending is one of the supported values for the API you are using. You can find detailed information in the request section of the API documentation.

APIs it applies to

212: No content to analyze

What does it mean?

The content that you provided to analyze could not be accessed or converted into HTML.

How do I fix it?

Check that the value you are sending is one of the supported values for the API you are using. You can find detailed information in the request section of the API documentation.

APIs it applies to

214: Wrong format: name of the parameter

What does it mean?

One of the parameters sent does not have the accepted format. The parameter with the wrong value will be specified in the error message.

How do I fix it?

The error message specified which parameter returned the error, so check the value you are sending and make sure it complies with the accepted values for it.

APIs it applies to

215: Timeout exceeded for service response

What does it mean?

The service has taken too long to respond and has exceeded the timeout set for the system.

How do I fix it?

The document sent to process may be to long to process in the time set as limit. If you are working in an on-premises installation and you are getting this error, consider changing the timeout values available in the configuration (REQUEST_TIMEOUT and ANALYTICS_REQUEST_TIMEOUT).

APIs it applies to

Contact Us

Do you have any other question? Contact us through our feedback section or send us an email.

Related links