Core eBL Request/Response StructuresThe PayPal SOAP API is built on core structures from the eBL schema that define required elements in all SOAP requests and responses:The following diagram represents the composition of the AbstractRequestType and AbstractResponseType elements.
Figure 2.1 AbstractRequestType is the base type definition of all PayPal SOAP requests.
IMPORTANT: You must set the value of the Version element for all requests to any PayPal API.
Table 2.1 A string representing the version of the PayPal Schema., specifically, the value the version attribute of the wsdl:definitions element . AbstractResponseType is the base type definition of all PayPal SOAP responses.For error codes and messages and their meanings, see Appendix A, “Error Codes and Messages for All PayPal APIs.”
Table 2.2 The date and time (UTC/GMT) the response was generated by the PayPal SOAP service as a result of processing a request. A token representing the application-level acknowledgement code. Contains one of the following enumerated values:
l Success: Request processing succeeded
l Failure: Request processing failed
l SuccessWithWarning: Request processing completed successfully but with some warning information in Errors that could be useful for the requesting application to process or record.
l FailureWithWarning: Request processing failed with some error and warning information that the requesting application should process to determine causes of failure.
l CustomCode: Reserved for internal or future use.
l ErrorCode: token defining the error code number
l ShortMessage: string containing the error message
l LongMessage: string describing the error message
l ErrorParameters: error parameters from the credit card processor. Returned only with DoDirectPaymentResponse.
l A string representing the version of the PayPal Schema, specifically, the value of the version attribute of the wsdl:definitions element .