Pera ServiceStack

StripeCustomerRequest

The following routes are available for this service:
GET,POST,PUT,DELETE,OPTIONS	/v1/StripeCustomer
GET,POST,PUT,DELETE,OPTIONS	/v1/StripeCustomer/{StripeCustomerId}

To override the Content-type in your clients HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/StripeCustomerRequest HTTP/1.1 
Host: api2.publicemployeeretirementassistance.com 
Content-Type: application/xml
Content-Length: length

<StripeCustomerRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/PeraServiceStackLibrary">
  <StripeCustomer>
    <StripeCustomer>
      <AgentId>0</AgentId>
      <StripeCustomerId>String</StripeCustomerId>
      <StripeMerchantId>0</StripeMerchantId>
    </StripeCustomer>
  </StripeCustomer>
  <StripeCustomerId>String</StripeCustomerId>
</StripeCustomerRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<StripeCustomerResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/PeraServiceStackLibrary">
  <ResponseStatus xmlns:d2p1="http://schemas.servicestack.net/types">
    <d2p1:ErrorCode>String</d2p1:ErrorCode>
    <d2p1:Message>String</d2p1:Message>
    <d2p1:StackTrace>String</d2p1:StackTrace>
    <d2p1:Errors>
      <d2p1:ResponseError>
        <d2p1:ErrorCode>String</d2p1:ErrorCode>
        <d2p1:FieldName>String</d2p1:FieldName>
        <d2p1:Message>String</d2p1:Message>
      </d2p1:ResponseError>
    </d2p1:Errors>
  </ResponseStatus>
  <StripeCustomer>
    <StripeCustomerExtended>
      <AgentId>0</AgentId>
      <StripeCustomerId>String</StripeCustomerId>
      <StripeMerchantId>0</StripeMerchantId>
      <StripeDetails />
    </StripeCustomerExtended>
  </StripeCustomer>
</StripeCustomerResponse>