| 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 .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
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/json
Content-Type: application/json
Content-Length: length
{"id":"00000000000000000000000000000000","partnerCode":"String","partnerName":"String","outboundUserName":"String","outboundPassword":"String","outboundUrl":"String","inboundUserName":"String","inboundPassword":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length "00000000000000000000000000000000"