Skip to main content
All methods in the Subscribe API return a Return object, which contains the return codes for the call. The Return object contains three data members:
  • returnCode: This data member contains a value that corresponds to a standard HTTP return code. For values of 400 or higher, assume that your call failed. The failure could be due to several reasons, such as an authentication failure or a Subscribe failure to find any objects that match your input. See the Standard Return Codes table below for a list of the most common return codes.
  • returnString: If returnCode indicates an error condition (a non-200 return code), your application can check returnString for further information. To help you debug your application in the development and production phases, use the Subscribe API to generate a log of returnString.
  • soapId: This ID is returned for certain calls to Vindicia, especially those made to submit a batch of data (for example, a batch of transactions or account activities) for ChargeGuard processing. This ID helps Vindicia track your batched data in Vindicia’s system and, if the ID is available, you should log it in your application. If an incident arises that requires troubleshooting by Vindicia, a Vindicia representative might ask you for this ID to determine the status of your data.
Some return strings contain information specific to the call for which the return was generated. In some cases, these will take the format:
where input-VID specifies the object or call to which the return error applies. In some cases, these will take the format:
where error-description more specifically explains the cause of the error. In both cases, variable text is displayed in bold-italic. The following table lists and describes the most common return codes. If a method returns different return codes, they are listed with the method. Parent topic:Subscribe API Overview