PayPal Adaptive Payments - 2012 Guía de usuario descargar pdf (Pagina 68)

Getting Started

HTTP Headers

68 August 7, 2012 Adaptive Payments Developer Guide

For SOAP messages, refer to the next section.

HTTP Headers for JSON, NVP, and XML Data Formats

SOAP Messages

To use Adaptive Payments with SOAP, include the HTTP headers for authentication as

described in the section Authentication and the application ID as described in the next section.

In addition, include the X-PAYPAL-MESSAGE-PROTOCOL header with a SOAP11 value.

The following is a header example for an Adaptive Payments API call for a SOAP message:

headers.put("X-PAYPAL-SECURITY-USERID", "tok261_biz_api.abc.com");

headers.put("X-PAYPAL-SECURITY-PASSWORD","1244612379");

headers.put("X-PAYPAL-SECURITY-SIGNATURE","lkfg9groingghb4uw5"

headers.put("X-PAYPAL-DEVICE-IPADDRESS", "168.212.226.204");

headers.put("X-PAYPAL-MESSAGE-PROTOCOL", "SOAP11");

headers.put("X-PAYPAL-APPLICATION-ID","APP-80W284485P519543T");

Below are the service name, port type, binding and location for SOAP as defined in the

Adaptive Payments WSDL.

<wsdl:service name="AdaptivePayments">

<wsdl:port name="AdaptivePaymentsSOAP11_http"

<binding="services:AdaptivePaymentsSOAP11Binding">

<soap:address location="https://svcs.paypal.com/AdaptivePayments" />

Specifying Application and Device Information

You also must identify the application. You can optionally identify other information

associated with the client and the API version:

Header Description

X-PAYPAL-REQUEST-DATA-FORMAT The payload format for the request.

Allowable values are:

 NV – Name-value pairs

 XML – Extensible markup language

 JSON – JavaScript object notation

X-PAYPAL-RESPONSE-DATA-FORMAT The payload format for the response.

Allowable values are:

 NV – Name-value pairs

 XML – Extensible markup language

 JSON – JavaScript object notation

1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 297 298

Sin comentarios

PayPal Adaptive Payments - 2012 Guía de usuario Pagina 68