optavalartaxgroup/{id}
-
api/optavalarataxgroup/{id}
-
GET
-
id = 5-digit zip code
-
-
api/optavalarataxgroup/search
-
POST
-
Body must contain the following JSON model
{ "Zip_Code": 33715, "TaxingGroupCode": null, "State": null, "County": null, "City": null, "Enforce_Filter": false } -
the 'Zip_Code' value is required
-
api/CustomerRecurring/GetRMRTrackingHistory
This returns all AR_RMR_Tracking records.
-
The returned model uses the already existing RMRTracking viewmodel, used by other 'api/CustomerRecurring' endpoints. SedonaCloud already had service logic to retrieve the AR_RMR_Tracking records and map to the RMRTracking viewmodel.
-
OData query options can be used to select history for a specific customer and to select only the fields required.
Note: The SO Recurring History view shows the RMR Amount as either a 'Decrease/Remove' or 'Increase/Add' entry. This is based on if the RMR Amount is > 0 (Increase/Add) or <0 (Decrease/Remove). The 'api/CustomerRecurring/GetRMRTrackingHistory' endpoint does not present these 2 columns, just RMRAmount. Consumers of the endpoint should analyze the positivity of the RMRAmount value for additional logic if necessary.
/api/paymentmerchant/captureauthorizedtransaction
New Capture endpoint utilizes the capture function in SedonaOffice, populating it with Forte Payments.
-
POST
-
Body must contain the following JSON model
{
"CustomerNumber": "10741",
"CustomerCreditCardId": 48,
"CustomerBankId": 0,
"ForteAuthorizationCode": "7TY485",
"ForteTransactionId": "02802880-78c9-4295-aa36-64999ef81eef",
"AuthorizedAmount": 16.52,
"Invoices": [
{
"InvoiceID": 1227,
"InvoiceNumber": 301318,
"NetDue": 16.52,
"Amount": 16.52
}
]
}
