
Web Services API Reference July 2006 25
PayPal Web Services API Architecture
SOAP Service Endpoints
Public/Private Key Encryption
Your security with the PayPal Web Services API relies on a set of public/private security keys
issued in the form of digital certificates by PayPal. These keys uniquely identify an API user to
prove his authorization to access PayPal Web Services. Each SOAP request is signed by your
private key, and PayPal Web Services processes a request only after authentication succeeds.
SSL Data Transport
All data must be transported over the Secure Hyper Text Transport Protocol (also known as
SHTTP or HTTPS), which relies on the Secure Sockets Layer (SSL) data communications
protocol.
SOAP Service Endpoints
Depending on your chosen authentication mechanism, your SOAP requests must be processed
by different service endpoints.
NOTE: For the correspondence between API calls and their service endpoints, see Table 2.8,
“API Overview by Business Function and Service Endpoint” on page 32.
<Subject> authorizing_
account_
emailaddress
The email address of a third-party for whom you are sending requests
to the PayPal Web Services API. Your API username must have been
granted permission by this third-party to make any particular PayPal
API request.
N
OTE: The <Subject> element must be included in the SOAP
header, even if you are not making a request on someone
else’s behalf. In this case, set
<Subject> with no value:
<Subject/>
T
ABLE 2.4 SOAP Service Endpoints
Authentication
Mechanism Live Production Endpoint Test (Sandbox) Endpoint
API Signature https://api-3t.paypal.com/2.0/
https://api-aa-3t.paypal.com/2.0/ https://api.sandbox.paypal.com/2.0/
https://api-aa.sandbox.paypal.com/2.0/
API Certificate https://api.paypal.com/2.0/
https://api-aa.paypal.com/2.0/
TABLE 2.3 RequesterCredentials Authentication Elements in SOAP Header
Element Value Description
Commenti su questo manuale