Your browser is out-of-date!

Update your browser to view this website correctly

×

Troubleshooting

What should I do when an error "Unable to Connect to tcp://store-url" occurs?

If this error occurs:

  • Check whether API2Cart IP is in the server’s firewall white list and restart the requests. (How to add IP to white list)
  • Your server’s characteristics isn’t suitable for particular shopping cart. Optimize your server configurations to establish proper work.
  • Increase the server’s RAM

What should I do when an error "Can't connect to URL" occurs?

If this error occurs:

  • Check whether API2Cart IP is in the server’s firewall white list and restart the requests. (How to add IP to white list)
  • Your server’s characteristics isn’t suitable for particular shopping cart. Optimize your server configurations to establish proper work.
  • Increase the server’s RAM

What should I do when an error "Unable to read response, or response is empty" occurs?

If this error occurs:

  • Check whether API2Cart IP is in the server’s firewall white list and restart the requests. (How to add IP to white list)
  • Your server’s characteristics isn’t suitable for particular shopping cart. Optimize your server configurations to establish proper work.
  • Increase the server’s RAM

What should I do when the error "The query was: SHOW TABLES" occurs?

If this error occurs, contact your server administrator to enable Base 64 support.

What should I do when an error "Store Database Validation Failed" occurs?

If this error occurs, it means that the cart or cart version, where the store is located, is not supported by API2Cart.

Another reason of the error formation is the database structure that has been changed because of the third-party module.

Can I find out more technical details on API error?

You can check Service Logs with this aim. Go to your account For Developers -> Service Logs.

Update item identificator is not specified.

Please, make sure you have passed an ID of the entity in the API request. Feel free to contact API2Cart Support Team in case if you still have any issues.

When using a method I get the error Store not Found

There are two possible reasons for that. Either you have entered the incorrect store_key or the store doesn’t exist. The list of available stores can be found on the following page: http://www.api2cart.com/app/stores.

API Method is not specified. What does it mean?

Please, specify the API method you would like to proceed working with. You can find the list of supported API methods here.

Duplicate record in database

We can’t create an entity with identified parameters, because of the SQL UNIQUE constraint - a row with a field which is meant to be unique already exists.

I received an error: ‘Entity already exists’. What does it mean?

This kind of error comes when API2Cart can’t create the entity due to shopping cart restriction. For example, if you’re trying to create a user with e-mail that is already registered.

‘Required parameter is not specified’. What does it mean?

Probably, you didn’t enter one of required parameters. To see the list of all the required and optional parameters, visit our Documentation section.

I get the message “Incorrect API Key” when using a method.

Check if you enter the correct APi Key. It can be found on the store management page http://www.api2cart.com/app/stores as well as here http://www.api2cart.com/app/profile.

How can I fix an error ‘Store URL is not reachable’?

Probably your firewall blocks our IP or the site is down. If you can access the site from your browser it means that your website is working. In this case, please, contact your hosting provider and ask him to add the API2Cart IP to the white list. If it still doesn’t help, contact our Support Team.

Store already exists. What does it mean?

API2Cart already has a store with the same URL. If you don’t see it in your profile, please contact us.

I got ‘Wrong FTP Store Path’ error. How can I fix it?

Double check the root folder where your store is located. If the shop is placed in subdomain of your site please indicate the subdomain folder. In case you can't solve this issue feel free to contact API2Cart Support Team.

Try send requests to store from other user.

The store belongs to another account. Please make sure there are no typing errors in the store_key parameter. If you have multiple API2Cart accounts, probably you’re using an api_key from a wrong one.

Store disconnect error

API2Cart can’t disconnect the store while you perform API request to it. If you see this error for a long time, most likely you are using a program, that makes periodical requests to the store through API2Cart. Please disable it before disconnecting. If you don’t know which specific program performs requests or how to disable it feel free to contact our Support Team.

I got an error: ‘Incorrect Store Key’. What shall I do?

In this case there are several simple steps that you can follow:

  • Re-upload a Connection Bridge file to store’s root folder using an FTP client. Click here for more info.
  • Change Store Key manually: in bridge2cart folder open config.php file with any kind of text editor (i.e. Notepad). In the bottom of the file you will be able to change your Store Key that you can find at http://www.api2cart.com/app/stores.
  • If none of the methods above are working don’t hesitate to contact us.

Search parameters are not specified. Where do I find them?

In order to use find methods you have to pass a find_value parameter, as in the following example:

http://api.api2cart.com:80/v1.0/product.find.json?api_key=a160c04a064f73a6ac38815768d8cbbb&store_key=ed58a22dfecb405a50ea3ea56979360d&find_value=a&find_params=regex

You can also use our Documentation to generate requests you need

How do I report a bug or request a new feature?

You can report a bug or request a new feature by contacting us. You are also welcome to contact our Customer Success manager at manager@api2cart.com in case of any issues.

Update parameters are not specified. What shall I do?

In order to update an entity please specify the attribute you want to change, for example &price=14.99. You can find the list of supported attributes in our Documentation section.

‘Incorrect FTP write permissions’ - what to do when I have this error?

API2Cart uses Bridge file that enables API interaction for some shopping carts. This folder should be uploaded to store directory via FTP client. In some cases a user may not have enough rights to change the corresponding folder. In order to fix it you have to change folder permissions:

  • 644 or 666 for "bridge.php", depending on your server configuration;
  • 755 or 777 for "/bridge2cart" folder, depending on your server configuration.

Standard HTTP Errors list

Redirection errors (3xx)

300 Multiple Choices - indicates multiple options for the resource that the client may follow.

301 Moved Permanently - This and all future requests should be directed to the given URL

302 Found - required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily")

303 See Other - The response to the request can be found under another URL using a GET method.

304 Not Modified - Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-Match

306 Switch Proxy - No longer used.Originally meant "Subsequent requests should use the specified proxy."

307 Temporary Redirect (since HTTP/1.1) - In this case, the request should be repeated with another URL; however, future requests should still use the original URL.

308 Permanent Redirect - the request, and all future requests should be repeated using another URL.

Client errors (4xx)

400 Bad Request - the request cannot be fulfilled due to bad syntax.

401 Unauthorized - similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

402 Payment Required - reserved for future use.

403 Forbidden - the request was a valid request, but the server is refusing to respond to it.

404 Not Found - the requested resource could not be found but may be available again in the future.

405 Method Not Allowed - a request was made of a resource using a request method not supported by that resource

406 Not Acceptable - the requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.

407 Proxy Authentication Required - the client must first authenticate itself with the proxy.

408 Request Timeout - the server timed out waiting for the request.

409 Conflict - indicates that the request could not be processed because of conflict in the request, such as an edit conflict in the case of multiple updates.

410 Gone - indicates that the resource requested is no longer available and will not be available again.

411 Length Required - the request did not specify the length of its content, which is required by the requested resource.

412 Precondition Failed - the server does not meet one of the preconditions that the requester put on the request.

413 Request Entity Too Large - the request is larger than the server is willing or able to process.

414 Request-URI Too Long - the URI provided was too long for the server to process.

415 Unsupported Media Type - the request entity has a media type which the server or resource does not support.

416 Requested Range Not Satisfiable - the client has asked for a portion of the file, but the server cannot supply that portion.

417 Expectation Failed - the server cannot meet the requirements of the Expect request-header field.

418 I'm a teapot - this code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.

419 Authentication Timeout - not a part of the HTTP standard, 419 Authentication Timeout denotes that previously valid authentication has expired.

420 Method Failure - not part of the HTTP standard, but defined by Spring in the HttpStatus class to be used when a method failed.

420 Enhance Your Calm - not part of the HTTP standard, but returned by version 1 of the Twitter Search and Trends API when the client is being rate limited.

422 Unprocessable Entity - the request was well-formed but was unable to be followed due to semantic errors.

423 Locked - еhe resource that is being accessed is locked.

424 Failed Dependency - еhe request failed due to failure of a previous request.

425 Unordered Collection - defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".

426 Upgrade Required - the client should switch to a different protocol such as TLS/1.0.

428 Precondition Required - the origin server requires the request to be conditional.

429 Too Many Requests - the user has sent too many requests in a given amount of time.

431 Request Header Fields Too Large - the server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

440 Login Timeout - a Microsoft extension. Indicates that your session has expired.

444 No Response - used in Nginx logs to indicate that the server has returned no information to the client and closed the connection.

449 Retry With - a Microsoft extension. The request should be retried after performing the appropriate action.

450 Blocked by Windows Parental Controls - a Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.

451 Unavailable For Legal Reasons - defined in the internet draft "A New HTTP Status Code for Legally-restricted Resources".

451 Redirect - used in Exchange ActiveSync if there either is a more efficient server to use or the server cannot access the users' mailbox.

494 Request Header Too Large - Nginx internal code similar to 431 but it was introduced earlier.

495 Cert Error - Nginx internal code used when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection.

496 No Cert - Nginx internal code used when client didn't provide certificate to distinguish it from 4XX in a log and an error page redirection.

497 HTTP to HTTPS - Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection.

499 Client Closed Request - used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back.

Server Errors (5xx)

500 Internal Server Error - a generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501 Not Implemented - the server either does not recognize the request method, or it lacks the ability to fulfill the request.

502 Bad Gateway - the server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 Service Unavailable - the server is currently unavailable (because it is overloaded or down for maintenance).

504 Gateway Timeout - the server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

505 HTTP Version Not Supported - the server does not support the HTTP protocol version used in the request.

506 Variant Also Negotiates - transparent content negotiation for the request results in a circular reference.

507 Insufficient Storage - the server is unable to store the representation needed to complete the request.

508 Loop Detected - the server detected an infinite loop while processing the request.

509 Bandwidth Limit Exceeded - this status code is not specified in any RFCs. Its use is unknown.

510 Not Extended - further extensions to the request are required for the server to fulfill it.

511 Network Authentication Required - the client needs to authenticate to gain network access.

520 Origin Error - this status code is not specified in any RFCs, but is used by Cloudflare's reverse proxies to signal an "unknown connection issue between CloudFlare and the origin web server" to a client in front of the proxy.

521 Web server is down - this status code is not specified in any RFCs, but is used by Cloudflare's reverse proxies to indicate that the origin web server refused the connection.

522 Connection timed out - this status code is not specified in any RFCs, but is used by Cloudflare's reverse proxies to signal that a server connection timed out.

523 Proxy Declined Request - this status code is not specified in any RFCs, but is used by Cloudflare's reverse proxies to signal a resource that has been blocked by the administrator of the website or proxy itself.

524 A timeout occurred - this status code is not specified in any RFCs, but is used by Cloudflare's reverse proxies to signal a network read timeout behind the proxy to a client in front of the proxy.

598 Network read timeout error - this status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.

599 Network connect timeout error - this status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.

HTTP Error Code 406, Not Acceptable

Web browsers request for information from the server, and when it is performed, it sends an Accept header. In case if the server is not able to send that data in the requested format in the Accept header, then the server sends the 406 Not Acceptable error.

Reasons

The 406 error can appear accordingly to your mod_security rule on the server. Mod_security is a security module of Apache web server, usually permitted automatically on all hosting profiles. In case if a site, page or even function violates one of the rules, server can send the 406 error.

How to Prevent

You can turn mod_security off. Also, there is a possibility to disable a specific rule or each domain individually. Thus, if you wish to disable mod_security, go to mod_security using modsec manager plugin in control panel.

Note: There may not be the option of turning mod_security on/off in your cPanel or dedicated servers. In such cases, use command line using SSH or contact tech support to enable/disable this option.

Need help or advice?

Schedule a call