Service Address
/DealerSale/GetScheduleList
Request Parameters
DealerSaleAuthentication
Parameter |
Explanation |
DealerCode(string) |
Dealer code issued by the Moka system |
Username (string) |
Api username given by Moka system |
Password (string) |
Api password given by Moka system |
CheckKey (string) |
The control key (DealerCode + "MK" + Username + "PD" + Password) is created by passing this information, combined as a String, through the SHA-256 hash algorithm.
Click here to go to the trial screen. |
Sample Request (JSON)
{
"DealerSaleAuthentication": {
"DealerCode": "xxx",
"Username": "xxx",
"Password": "xxx",
"CheckKey": "aabbccddeeff"
}
}
Successful Request Result
If the sent request data has been processed successfully in Moka, "Success" information is written in the "ResultCode" field of the return object . The "Data" field contains the result of the returned operation. You can continue your flows by checking the information in "Data" .
Parameter |
Explanation |
SaleScheduleListCount (integer) |
Number of dealer's time programs |
SaleScheduleList (Array) |
List of dealer's schedules
DealerSaleScheduleId (integer) | On the Moka side, it is the Unique ID of the time program |
ScheduleName (string) | Name of the time program (ex: "Monthly payment") (Max 100) |
DailyWeeklyMonthly (integer) | 1: Daily shot 2: Weekly shot 3: Monthly shot |
EveryX (integer) | On how many days, week or month will the payment be made (value of 1 means every day, week or month, value of 2 means every 2 days, every 2 weeks or every 2 months.) |
DaysOfWeek (string) | What days of the week will you shoot? 1: Monday 7: Sunday. If more than one day is to be shot, it is written as separated by commas. |
DaysOfMonth (string) | What days of the month will you shoot? If more than one day is to be shot, it is written as separated by commas.. |
|
Successful Result Example
{
"Data": {
"SaleScheduleListCount": 1,
"SaleScheduleList": [
{
"DealerSaleScheduleId": 1005,
"ScheduleName": "newschedule",
"DailyWeeklyMonthly": 2,
"EveryX": 1,
"DaysOfWeek": "1,2,3",
"DaysOfMonth": ""
}
]
},
"ResultCode": "Success",
"ResultMessage": "",
"Exception": null
}
Failed Request Result
If the sent request data could not be processed in Moka streams, the "ResultCode" field of the return object contains one of the error codes in the table below.
When an unexpected software error occurs, EX is written in the "ResultCode" field and the error message (Exception) is displayed in the "ResultMessage" field
In both cases, the "Data" object arrives as null.
ResultCode | Explanation |
DealerSale.GetScheduleList.InvalidRequest | The CheckKey may be bad, or the object may be bad, or the JSON may be corrupt. |
DealerSale.GetScheduleList.NoDataFound | Data not found. |
EX | An unexpected error has occurred |
Example of Failed Result
{
"Data": null,
"ResultCode": "DealerSale.GetScheduleList.NoDataFound",
"ResultMessage": "",
"Exception": null
}