Invalid Request Feel Free to Try Again With a Valid Token Song Request
API Mistake Codes
The iGolder API may return 1 of the following error.
Authentication Errors
These are errors when invoking a spider web service without proper settings. To protect your account confronting hackers, must Enable Automation to utilise any iGolder API. So, you must grant access to the IP address accessing your account, otherwise you will receive any of the following fault:
| Error Name | Error Description |
|---|---|
| ErrApiSubAccountIdMissing (error code 601) | Missing Sub-Business relationship ID The XML data structure is missing the element <SubAccountId> which must be a valid account identifier. The sub-account ID can be establish at the page in https://www.igolder.com/business relationship/details.aspx in the Automation section. |
| ErrSubAccountNotFound (error code 602) | Sub-Account Non Found There is no respective sub-account identifier matching the XML element <SubAccountId>. To observe your sub-account ID, visit the Automation section at https://www.igolder.com/account/details.aspx. This error happens when you supply an invalid/unknown sub-account identifier. Developers oftentimes get this fault when switching from "demo" to "alive" manner. For case, a valid sub-business relationship ID at http://demo.iGolder.com is invalid at https://www.iGolder.com. If you lot switch your web service handler from http://demo.iGolder.com/api.ashx to https://world wide web.iGolder.com/api.ashx, and so y'all have to update the sub-account ID, otherwise you lot will get the error ErrSubAccountNotFound. For more information, visit Where can I notice my Sub-Account ID and Security Token ID? |
| ErrApiSecurityTokenIdMissing (error code 603) | Missing Security Token ID The XML element <SecurityTokenId> is not found. The Security Token ID tin exist institute at the page https://www.igolder.com/business relationship/details.aspx in the Automation section. If you need help formatting your XML request, feel free to download our Automation Tool. This tool contains the entire API Reference to create valid XML requests. |
| ErrApiSecurityTokenIdInvalid (error lawmaking 604) | Invalid Security Token ID The XML element <SecurityTokenId> contains an invalid security token identifier. The Security Token ID can be plant at the page https://www.igolder.com/account/details.aspx in the Automation department. This error happens if you lot enter an invalid Security Token ID, or if you disable automation and enable automation over again. Each time yous enable automation, iGolder generates a new Security Token ID. If y'all feel your Security Token ID has been compromised, then disable automation and enable automation again. or more information, visit Where can I notice my Sub-Account ID and Security Token ID? A Security Token ID is your automation password. For security purpose, iGolder uses a different password to login to your account and for web service APIs. This manner, someone knowing your automation password (your SecurityTokenId) will exist unable to login to to your business relationship and make an unauthorized transaction. |
| ErrApiDisabled (mistake code 605) | Automation Disabled The account Alice is not enabled for API automation. For security reasons, iGolder disables automation on every new account. To enable automation, visit https://world wide web.igolder.com/business relationship/details.aspx and click on the push button 'Enable Automation'. This fault happens when y'all attempt to invoke a web service (encounter API Reference)) on an account you have not yet enabled automation. For more details, visit Enable Automation. |
| ErrApiUnauthorizedIpAddress (error code 606) | The IP accost 124.14.127.190 is non authorized for automation The IP accost 124.14.127.190 does not have the required authorization to access the account Alice. To enable automation from computer 124.14.127.190, you must grant access to the IP accost 124.xiv.127.190. Follow the link beneath and click on "Approve IP Address" for granting access to the IP address 124.fourteen.127.190. This mistake message happens on your kickoff attempt to invoke a web service (see API Reference)). In the example in a higher place, the IP accost is 124.14.127.190 and the account name is Alice. In your instance, the IP address volition be the IP of your computer or server, and the account proper name will be the account name corresponding to the SubAccountId. You may also get this message if your estimator (or server) changes IP accost. If you are on a dialup connectedness, or uses a high-speed Internet connectedness, it is possible your ISP changes your IP address from time to time. In that instance, you lot accept to approve your new IP address to grant automation admission to your calculator. If you use our Automation Tool, simply click on the hyperlink at the bottom of the dialog and the link will automatically take care of granting automation to your IP accost. For more details, visit Approving Pending IP Authority. |
Shopping Cart Interface Errors
The Shopping Cart Interface may return one of the following additional error.
| Mistake Name | Error Description |
|---|---|
| ErrTransactionNotApproved (error code 450) | Transaction Not Approved The customer rejected the transaction. To have the transaction, click on the push button "Two authorize this payment" on the iGolder website. Larn more > |
| ErrTransactionAlreadyProcessed (error code 451) | Transaction Already Processed The merchant already processed your transaction and accepted your payment. This bulletin is a protection so you are non billed twice for the aforementioned transaction. Learn more > |
Gold Transfer Error
| Error Message | Error Description |
|---|---|
| Duplicate Transaction Detected | The value 889af6eb56c642fcb7c3b45271a8842f specified in the chemical element <TransferId> is already in the database, and therefore not unique. Please generate a new GUID for the <TransferId>. This mistake is returned only by the spider web service <TransferRequest>. |
| Payee Name Missing | iGolder requires a valid <PayeeName> to create a new account for email Alice@iGolder.com. This error occurs when y'all attempt to brand a payment to an email non present in our database. |
Very Rare Errors
These errors are extremely rare; they occurs just during critical conditions. Nosotros recommend displaying the <ErrorTitle> and <ErrorDescription> to the customer and suggesting to try again.
| Error Proper noun | Error Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ErrApiUnknownRequest (fault lawmaking 607) | Unknown Web Service Request The spider web service request named <GetServiceApiXYZ> is unknown to iGolder. Please visit our API Reference to determine what web services are available to yous. This error happens when you invoke an unknown API. Make sure spelled the web service name properly. To get the list of APIs available, visit visit our API Reference. | ||||||||||||
| ErrApiInvalidXmlFormat (error lawmaking 600) | Invalid XML Request The XML data structure format is invalid and/or contains illegal characters. The get-go tag <ABC> on line two does not match the finish tag </ABCD> (Line two, position 15). This mistake happens when you supply an invalid XML request. Brand sure all your XML elements are matching and you properly encode the following XML escape characters:
| ||||||||||||
| ErrUnknown (error code 999) | Unknown Internal Error An unknown internal fault occurred. This mistake happens when iGolder detected an internal problem, however was unable to classify the fault. When iGolder is unable to give a proper name to an error, iGolder returns ErrUnknown. If y'all tin reproduce this fault, delight contact iGolder and we volition do our all-time to find a solution. |
Processing XML Errors
iGolder returns all errors in the XML format, where the root node is <Fault>. Run across below for an case of an error message.
Error XML Example
<Error> <ErrorCode>604</ErrorCode> <ErrorName>ErrApiSecurityTokenIdInvalid</ErrorName> <ErrorTitle>Invalid Security Token ID</ErrorTitle> <ErrorDescription>The XML element 'SecurityTokenId' contains an invalid security token identifier. The Security Token ID can be found at the page https://www.igolder.com/account/details.aspx in the Automation section.</ErrorDescription> <UrlAction>https://world wide web.igolder.com/account/details.aspx?id=cbcc42cd9d82498285099a7c457f8c9b&ShowAutomation=one</UrlAction> <UrlHelp>https://www.igolder.com/developer/API-error-codes/#ErrApiSecurityTokenIdInvalid</UrlHelp> </Error>
Beefcake of an error message
| Element Name | Element Description |
|---|---|
| ErrorCode | Permanent numeric value assigned to the error. This value is useful if you wish to store errors using an integer, or if your development language requires a numeric "switch" statement. |
| ErrorName | Permanent symbolic proper noun representing the error. The ErrorName is friendlier to empathise than the ErrorCode. Regardless of the locale, the error name volition always remain the aforementioned. |
| ErrorTitle | Title of the error. For convenience, iGolder provides a title for every fault. The error championship may be displayed as a caption or in bold before displaying the error description. Depending on the context of the user, the error championship may exist localized in a foreign language. |
| ErrorDescription | Detailed text regarding the error. The error description may be several lines long, to fully describe the error. The error description may be localized in a foreign language. |
| UrlAction | Action hyperlink to help fixing the error. Sometimes the UrlAction is absent-minded, as some errors cannot be fixed past just clicking on an hyperlink. |
| UrlHelp | Hyperlink to the technical documentation regarding the fault. |
Using iGolder Automation Test Tool
The tool iGolderAutomationTool.exe was designed for testing the spider web services and brandish errors. If an error occurred, yous tin click on the URL at the bottom of the tool to fix the error (UrlAction) or to view the documentation (UrlHelp).
In the example above, the IP address is non authorized to access Alice'southward account via spider web service. The tool displays the link from UrlAction, assuasive the user to grant access to the IP address. The user simply has to click on the hyperlink at the bottom right of the screen to approve the IP address. To learn more, visit iGolder Automation Test Tool.
Source: https://www.igolder.com/developer/api-error-codes/
0 Response to "Invalid Request Feel Free to Try Again With a Valid Token Song Request"
ارسال یک نظر