Could Not Retrieve Your Location. Please Try Again ïâ¿â¼
This article contains some common issues that users may experience when start trying to work with the Infoplus API and how to fix them.
If you are having trouble getting a new integration to work, delight see if you're running into whatever of the issues listed here. If you're still having issues, please get in touch with our Support Squad for further assistance.
Missing Tables/Unable to Access Fields
Make sure you are using the beta version (not v1.0/v2.0) to access all tables and fields inside the nearly current version of Infoplus WMS.
Permission Issues
If you lot are receiving a 500 mistake when you are querying a table for information, exist certain to check the permissions of the API user on the Userlevel.
If you are querying a table and receiving a 200 response but not receiving data, verify that your API user has permissions on the User level to fully access the table you are querying.
If you lot are setting up a new Line of Business and continue to encounter endpoints and data that practice not correlate with their LOB, verify the API'southward User and Role permissions. If y'all added an incorrect Role, remove the incorrect Part.You lot will also need to delete the old API central and create a new API fundamental for the new Role permissions to have consequence.
Querying Using coil
If you are receiving an invalid character error when querying a table using a cURL method such as, ?filter=sku like "P0000%", yous may receive a 400 error. This ways that operation is currently non available for that table.
Content-Type: application/json
The Infoplus API uses merely application/json as its Content-Blazon, for all types of requests (i.east., Get, POST, PUT).
This means that whatever requests to the API which include a body (i.e., POST or PUT) MUST include an HTTP header of "Content-Type:awarding/json". Furthermore, the body content of any POST or PUT's must be a well-formed JSON object (not an XML document, form-data, x-www-class-urlencoded, or annihilation else).
Similarly, since all Infoplus API endpoints render Content-Type:application/json, your requests should include an HTTP header of "Have:application/json" (or an equivalent, such as "Accept:*/json" or "Take:*/*").
If yous violate any of these Content-Type requirements, yous will virtually likely receive an invalid response, with an HTTP 503 response code.
SSL Certificate Trust
The Infoplus API requires that all requests be issued over HTTPS, and the SSL document with which Infoplus signs all requests is one issued past AWS's Certificate Manager. This can potentially cause an issue for API clients whose local security trust stores are not updated to exist aware of the intermediate certificates in our trust chain, which were released in 2015.
This fault may present itself (for a customer using a Coffee application) equally javax.cyberspace.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path edifice failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to detect valid certification path to requested target. Other client programming environments may offering similar error messaging.
If you are running into this type of error, the way to solve information technology is to update your application/server to accept our SSL document (specifically, the intermediate certificates in our certificate's trust chain). Oracle offers this path to update a coffee installation.
Timezone Behavior
There is a bug in the implementation of timezones in versions 1, 2, and the current beta of the Infoplus API, where times are indicated as GMT/UTC, despite their values really being shifted to exist United states of america Primal time. For instance, a value returned by the Infoplus API of 2020-07-04T16:00:00.000Z should actually exist: 2020-07-04T21:00:00.000Z (it is off by the US-Key timezone offset, which is 5 hours during daylight saving time, 6 hours during standard time).
To avert this behavior, and get proper timezone behavior from the Infoplus API, y'all tin include the HTTP header:X-Infoplus-Proper-Timezone-Behavior with a value of 1 in your API requests.
Non-ASCII Characters
If you are receiving a 400 mistake from the API, it may exist because you are trying to submit a Non-ASCII graphic symbol. The Infoplus API does not support Non-ASCII characters because the backend database will non accept them. One way that you can test your call is past using a ASCII checker similar WISC ACSII Tester.
Example Error:
Response Code
400
Response Message
{errors=[An error has occurred saving this Detail. Please endeavour again or contact Back up.]}
Examples of Non-ASCII Characters:
Character | Description |
---|---|
€ | euro sign |
‚ | unmarried low-ix quotation mark |
ƒ | lowercase letter f with claw |
„ | double low-9 quotation mark |
… | horizontal ellipsis |
† | dagger |
‡ | double dagger |
ˆ | modifier letter of the alphabet circumflex accent |
‰ | per mille sign |
Š | uppercase letter S with caron |
‹ | single left-pointing angle quotation |
Œ | capital ligature OE |
Ž | captial letter of the alphabet Z with caron |
' | left unmarried quotation mark |
' | right single quotation mark |
" | left double quotation mark |
" | right double quotation mark |
• | bullet |
– | en dash |
— | em dash |
˜ | tilde |
™ | TM trademark sign |
š | lowercase letter S with caron |
› | right-pointing angle quotation marking |
œ | lowercase ligature oe |
ž | lowercase letter z with caron |
Ÿ | uppercase letter Y with diaeresis |
non-breaking space | |
¡ | inverted assertion mark |
¢ | cent sign |
£ | pound sign (currency) |
¤ | currency sign |
¥ | yen/yuan sign |
¦ | broken vertical bar |
§ | section sign |
¨ | diaeresis |
© | copyright sign |
ª | feminine ordinal indicator |
« | left double angle quotation mark (guillemet) |
¬ | not sign (logic) |
| soft/discretionary hyphen |
® | registered trademark sign |
¯ | spacing macron / overline |
° | degree sign |
± | plus/minus sign |
² | superscript two (squared) |
³ | superscript three (cubed) |
´ | acute accent |
µ | micro sign |
¶ | paragraph sign (pilcrow) |
· | middle dot |
¸ | cedilla |
¹ | superscript i |
º | masculine ordinal indicator |
» | correct double angle quotation marking (guillemet) |
¼ | 1-quarter fraction (1 over 4) |
½ | i-half fraction (1 over 2) |
¾ | 3-quarters fraction (3 over 4) |
¿ | inverted question mark |
À | upper-case letter A with grave accent |
Á | capital letter A with acute emphasis |
 | capital letter A with circumflex |
à | uppercase A with tilde |
Ä | majuscule letter of the alphabet A with diaeresis |
Å | upper-case letter letter A with ring above |
Æ | capital AE ligature |
Ç | majuscule letter C with cedilla |
È | uppercase alphabetic character E with grave accent |
É | majuscule E with acute emphasis |
Ê | capital letter E with circumflex |
Ë | capital letter East with diaeresis |
Ì | upper-case letter letter I with grave emphasis |
Í | capital letter of the alphabet I with astute accent |
Î | upper-case letter letter of the alphabet I with circumflex |
Ï | upper-case letter alphabetic character I with diaeresis |
Ð | majuscule letter ETH(Dogecoin symbol) |
Ñ | capital letter N with tilde |
Ò | upper-case letter letter of the alphabet O with grave emphasis |
Ó | upper-case letter O with acute accent |
Ô | uppercase O with circumflex |
Õ | capital letter O with tilde |
Ö | capital letter letter O with diaeresis |
× | multiplication sign |
Ø | capital letter O slash |
Ù | capital letter U with grave accent |
Ú | upper-case letter U with acute accent |
Û | capital letter letter U with circumflex |
Ü | capital letter U with diaeresis |
Ý | capital letter letter Y with acute accent |
Þ | capital letter THORN |
ß | lowercase letter sharp s (Eszett /scharfes Due south ) |
à | pocket-size letter a with grave emphasis |
á | lowercase letter a with acute accent |
â | lowercase letter of the alphabet a with circumflex |
ã | lowercase letter a with tilde |
ä | lowercase alphabetic character a with diaeresis |
å | lowercase letter a with ring in a higher place |
æ | lowercase ae ligature |
ç | lowercase letter c with cedilla (cé cédille) |
è | lowercase letter e with grave accent |
é | lowercase alphabetic character due east with astute emphasis |
ê | lowercase letter eastward with circumflex |
ë | lowercase letter of the alphabet e with diaeresis |
ì | lowercase letter of the alphabet i with grave accent |
í | lowercase letter i with acute accent |
î | lowercase alphabetic character i with circumflex |
ï | lowercase letter i with diaeresis |
ð | lowercase letter eth |
ñ | lowercase letter n with tilde |
ò | lowercase letter o with grave accent |
ó | lowercase letter of the alphabet o with astute accent |
ô | lowercase letter o with circumflex |
õ | lowercase letter of the alphabet o with tilde |
ö | lowercase letter o with diaeresis |
÷ | division sign |
ø | lowercase alphabetic character o with slash |
ù | lowercase letter u with grave accent |
ú | lowercase letter of the alphabet u with acute accent |
û | lowercase letter u with circumflex |
ü | lowercase letter of the alphabet u with diaeresis |
ý | lowercase letter y with acute emphasis |
þ | lowercase letter thorn |
ÿ | lowercase alphabetic character y with diaeresis |
Source: https://www.infopluscommerce.com/knowledge-base/troubleshooting-the-infoplus-api
0 Response to "Could Not Retrieve Your Location. Please Try Again ïâ¿â¼"
Post a Comment