EppScheduling
Click here for a complete list of operations.
CreateSchedule
Test
The test form is only available for requests from the local machine.SOAP 1.1
The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.
POST /EppScheduling.asmx HTTP/1.1 Host: services.peloton-technologies.com Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: "http://www.peloton-technologies.com/CreateSchedule" <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <CreateSchedule xmlns="http://www.peloton-technologies.com/"> <createScheduleRequest> <ClientId>int</ClientId> <AccountName>string</AccountName> <Password>string</Password> <ApplicationName>string</ApplicationName> <ScheduleId>string</ScheduleId> <ScheduleName>string</ScheduleName> <Activate>boolean</Activate> <PaymentMethodTypeCode>int</PaymentMethodTypeCode> <ScheduleTypeCode>int</ScheduleTypeCode> <TransactionTypeCode>int</TransactionTypeCode> <AmountCalculationTypeCode>int</AmountCalculationTypeCode> <PaymentTargetId>string</PaymentTargetId> <OrderNumber>string</OrderNumber> <PaymentAmount>decimal</PaymentAmount> <TotalAmount>decimal</TotalAmount> <CurrencyCode>string</CurrencyCode> <InitialPaymentOnActivation>boolean</InitialPaymentOnActivation> <TragetDateTypeCode>int</TragetDateTypeCode> <StartDateTime>dateTime</StartDateTime> <EndDateTime>dateTime</EndDateTime> <PaymentFrequencyTypeCode>int</PaymentFrequencyTypeCode> <PaymentFrequencyIntervalTypeCode>int</PaymentFrequencyIntervalTypeCode> <PaymentFrequencyRecurrenceFactorTypeCode>int</PaymentFrequencyRecurrenceFactorTypeCode> <TotalNumberOfOccurrences>int</TotalNumberOfOccurrences> <LanguageCode>string</LanguageCode> <Reference1>string</Reference1> <Reference2>string</Reference2> <Reference3>string</Reference3> <Reference4>string</Reference4> <Reference5>string</Reference5> </createScheduleRequest> </CreateSchedule> </soap:Body> </soap:Envelope>
HTTP/1.1 200 OK Content-Type: text/xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <CreateScheduleResponse xmlns="http://www.peloton-technologies.com/"> <CreateScheduleResult> <Success>boolean</Success> <Message>string</Message> <MessageCode>int</MessageCode> <ScheduleId>string</ScheduleId> <StateCode>int</StateCode> <NextActionDatetime>dateTime</NextActionDatetime> <NextScheduleDatetime>dateTime</NextScheduleDatetime> </CreateScheduleResult> </CreateScheduleResponse> </soap:Body> </soap:Envelope>
SOAP 1.2
The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.
POST /EppScheduling.asmx HTTP/1.1 Host: services.peloton-technologies.com Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:Body> <CreateSchedule xmlns="http://www.peloton-technologies.com/"> <createScheduleRequest> <ClientId>int</ClientId> <AccountName>string</AccountName> <Password>string</Password> <ApplicationName>string</ApplicationName> <ScheduleId>string</ScheduleId> <ScheduleName>string</ScheduleName> <Activate>boolean</Activate> <PaymentMethodTypeCode>int</PaymentMethodTypeCode> <ScheduleTypeCode>int</ScheduleTypeCode> <TransactionTypeCode>int</TransactionTypeCode> <AmountCalculationTypeCode>int</AmountCalculationTypeCode> <PaymentTargetId>string</PaymentTargetId> <OrderNumber>string</OrderNumber> <PaymentAmount>decimal</PaymentAmount> <TotalAmount>decimal</TotalAmount> <CurrencyCode>string</CurrencyCode> <InitialPaymentOnActivation>boolean</InitialPaymentOnActivation> <TragetDateTypeCode>int</TragetDateTypeCode> <StartDateTime>dateTime</StartDateTime> <EndDateTime>dateTime</EndDateTime> <PaymentFrequencyTypeCode>int</PaymentFrequencyTypeCode> <PaymentFrequencyIntervalTypeCode>int</PaymentFrequencyIntervalTypeCode> <PaymentFrequencyRecurrenceFactorTypeCode>int</PaymentFrequencyRecurrenceFactorTypeCode> <TotalNumberOfOccurrences>int</TotalNumberOfOccurrences> <LanguageCode>string</LanguageCode> <Reference1>string</Reference1> <Reference2>string</Reference2> <Reference3>string</Reference3> <Reference4>string</Reference4> <Reference5>string</Reference5> </createScheduleRequest> </CreateSchedule> </soap12:Body> </soap12:Envelope>
HTTP/1.1 200 OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:Body> <CreateScheduleResponse xmlns="http://www.peloton-technologies.com/"> <CreateScheduleResult> <Success>boolean</Success> <Message>string</Message> <MessageCode>int</MessageCode> <ScheduleId>string</ScheduleId> <StateCode>int</StateCode> <NextActionDatetime>dateTime</NextActionDatetime> <NextScheduleDatetime>dateTime</NextScheduleDatetime> </CreateScheduleResult> </CreateScheduleResponse> </soap12:Body> </soap12:Envelope>