| GET | /members/PaymentOption |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ClientId | query | int | No | |
| GroupId | query | string | No | |
| UserId | query | string | No | |
| BhUserId | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ClientId | form | int | No | |
| GroupId | form | string | No | |
| ErrorCode | form | int | No | |
| ErrorMessage | form | string | No | |
| PaymentOption | form | List<PaymentOptions> | No | |
| IsError | form | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BhUserId | form | int | No | |
| UserId | form | string | No | |
| PaymentOption | form | string | No |
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.
GET /members/PaymentOption HTTP/1.1 Host: devapi.billhighway.com Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ClientId":0,"GroupId":"String","ErrorCode":0,"ErrorMessage":"String","PaymentOption":[{"BhUserId":0,"UserId":"String","PaymentOption":"String"}],"IsError":false}