| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| GuestPayeeIds | query | List<int> | No | |
| ChaperonePayeeIds | query | List<int> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | StripeDataHelper | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| AuthorizerRole | form | string | No | |
| AuthorizerId | form | int | No | |
| GuestPayeeIds | form | List<int> | No | |
| ChaperonePayeeIds | form | List<int> | No | |
| GuestPayeeIdsValidated | form | List<int> | No | |
| ChaperonePayeeIdsValidated | form | List<int> | No | |
| AmountPerPayee | form | decimal | No | |
| TotalAmountDecimal | form | decimal | No | |
| TotalAmountInt | form | int | 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.
POST /json/reply/CalculateCharges HTTP/1.1
Host: api.lsu-staging.abodehms.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"guestPayeeIds":[0],"chaperonePayeeIds":[0]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}