efun.id.api

QrCodeInitRequest

The following routes are available for this service:
POST	/api/v1/qrcode-init

**QrCodeInitRequest** Parameters:
Name	Parameter	Data Type	Required	Description
Captcha	body	string	Yes
Price	body	int	No

**BaseResponse<List>** Parameters:
Name	Parameter	Data Type	Required
Code	form	int	No
Message	form	string	No
Data	form	List<BannerListResponse>	No

**BannerListResponse** Parameters:
Name	Parameter	Data Type	Required
Id	form	int	No
Title	form	string	Yes
Image	form	string	Yes
Url	form	string	Yes
Publish	form	bool	No
PublishDate	form	DateTime	No
OrderIndex	form	int	No

To override the Content-type in your clients, use the 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 /api/v1/qrcode-init HTTP/1.1 
Host: efun-id-api-sandbox.efun.vn 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<QrCodeInitRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/efun.id.api.ServiceModel">
  <Captcha>String</Captcha>
  <Price>0</Price>
</QrCodeInitRequest>

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

<BaseResponseOfQrCodeResponse53LsApX4 xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/efun.id.api.ServiceModel">
  <Code>0</Code>
  <Data xmlns:d2p1="http://schemas.datacontract.org/2004/07/efun.id.data.Models">
    <d2p1:EcollectionCodeName>String</d2p1:EcollectionCodeName>
    <d2p1:Note>String</d2p1:Note>
    <d2p1:PayerName>String</d2p1:PayerName>
    <d2p1:PaymentDueDate>0001-01-01T00:00:00</d2p1:PaymentDueDate>
    <d2p1:Price>0</d2p1:Price>
    <d2p1:QrCodeData>String</d2p1:QrCodeData>
    <d2p1:RefId>String</d2p1:RefId>
  </Data>
  <Message>String</Message>
</BaseResponseOfQrCodeResponse53LsApX4>