PUT | /partners/{id} | Updates an existing partner. Fails if the partner doesn't exist. |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | path | Guid | Yes | The partner id |
PartnerCode | body | string | Yes | The partner code. |
PartnerName | body | string | Yes | The partner name. |
OutboundUserName | body | string | No | The outbound username for this partner. |
OutboundPassword | body | string | No | The outbound password for this partner. |
OutboundUrl | body | string | No | The outbound url for this partner. |
InboundUserName | body | string | No | The inbound username for this partner. |
InboundPassword | body | string | No | The inbound password for this partner. |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /partners/{id} HTTP/1.1
Host: api.paylock.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UpdatePartner xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BootView.WebApi.ServiceModel">
<Id>00000000-0000-0000-0000-000000000000</Id>
<InboundPassword>String</InboundPassword>
<InboundUserName>String</InboundUserName>
<OutboundPassword>String</OutboundPassword>
<OutboundUrl>String</OutboundUrl>
<OutboundUserName>String</OutboundUserName>
<PartnerCode>String</PartnerCode>
<PartnerName>String</PartnerName>
</UpdatePartner>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <guid xmlns="http://schemas.microsoft.com/2003/10/Serialization/">00000000-0000-0000-0000-000000000000</guid>