Quote & Lease Operations API: ExecuteReportWebService Reg Renewals
API endpoints for quote (Qt_*) and lease (Qq_*) operations and fleet reports
ExecuteReportWebService Reg Renewals
This API allows you to run the Registration Renewals Report available in the Fleet / Administration / Reports menu.
Supplementary SWAGGER documentation is available here: api.test.catch-e.com/docs/#/Web%20Services/executeReportWebService
Enable
Go to Setup / Reference Data β gbcontrols) and find the "apiwebserviceswrapper_login" control.
Populate this control with a 'web_services' user login and password.
This user will be used to run the API from within code.
Permissions
To run this API, the nominated 'web-services' role needs to be given permission.
If you are not actively using the API, leave the permission off for better security.
Go to Roles / Apis and check on WebServices.
Authentication
Authenticate with the API before running this API.
HTTP Method
Use the HTTP Method 'POST' for consuming this web service.
URL Examples
https://api.test.catch-e.com/web-services/gb/reporting/executeReportBody (JSON)
JSON Example
{ "report_path": "/core/fleet/reports/pdf_reg_renewals.phpo", "report_format": "PDF", "parameters": { "date_filter": "31/01/2025", "t11.user_login": "--All--", "t6.client_group_code": "--All--", "t3.client_code": "--All--", "t1.cost_centre": "--All--", "t5.posting_map_code": "--All--", "filter_suspend_date": "00/00/0000" }, "arguments": { "use_supplied_report_path_flag": "no" }}Response Details
{ "validation_messages": { "report_path": { "notInArray": "Unsupported report path specified" }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"}| Incorrect "report_path" has been entered. | |
{ "validation_messages": { "report_format": { "notInArray": "The input was not found in the haystack" }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"| The "report_path" entered is not in the allowable list of options. | |
{ "validation_messages": { "web_service_error": { "CATCH_E_ERROR_NOTHING_TO_REPORT": "" } }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"}|| A Parameter is missing, or an incorrect value has been entered. | |
{ "validation_messages": { "web_service_error": { "CATCH_E_ERROR_AUTHENTICATION_FAILED": "" } }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"}|| This response could be due to incorrect authentication credentials, or your authentication token has timed out. If you are consistently receiving this error, please raise a ticket with your Account Manager. Please supply the complete Request & Response payloads. [Warning:] Please remember to NEVER send user login credentials when sending a ticket request. Catch-e staff have our own credentials we can use to de-bug these tickets. |
| 403 - Forbidden | | |
|{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Forbidden", "status": 403, "detail": "Forbidden"}| You do not have permissions for this request. |
ExecuteReportWebService Service Overdue
This API allows you to run the Service Overdue Report available in the Fleet / Administration / Reports menu.
Supplementary SWAGGER documentation is available here: api.test.catch-e.com/docs/#/Web%20Services/executeReportWebService
Enable
Go to Setup / Reference Data β gbcontrols) and find the "apiwebserviceswrapper_login" control.
Populate this control with a 'web_services' user login and password.
This user will be used to run the API from within code.
Permissions
To run this API, the nominated 'web-services' role needs to be given permission.
If you are not actively using the API, leave the permission off for better security.
Go to Roles / Apis and check on WebServices.
Authentication
Authenticate with the API before running this API.
HTTP Method
Use the HTTP Method 'POST' for consuming this web service.
URL Examples
https://api.test.catch-e.com/web-services/gb/reporting/executeReportBody (JSON)
JSON Example
{ "report_path": "/core/fleet/reports/pdf_service_overdue.phpo", "report_format": "PDF", "parameters": { "date_filter": "02/12/2024", "t11.user_login": "--All--", "t6.client_group_code": "--All--", "t3.client_code": "--All--", "t1.cost_centre": "--All--", "t5.posting_map_code": "--All--", "filter_suspend_date": "00/00/0000" }, "arguments": { "use_supplied_report_path_flag": "no" }}Response Details
{ "validation_messages": { "report_path": { "notInArray": "Unsupported report path specified" }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"}| Incorrect "report_path" has been entered. | |
{ "validation_messages": { "report_format": { "notInArray": "The input was not found in the haystack" }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"| The "report_path" entered is not in the allowable list of options. | |
{ "validation_messages": { "web_service_error": { "CATCH_E_ERROR_NOTHING_TO_REPORT": "" } }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"}|| A Parameter is missing, or an incorrect value has been entered. | |
{ "validation_messages": { "web_service_error": { "CATCH_E_ERROR_AUTHENTICATION_FAILED": "" } }, "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Unprocessable Entity", "status": 422, "detail": "Failed Validation"}|| This response could be due to incorrect authentication credentials, or your authentication token has timed out. If you are consistently receiving this error, please raise a ticket with your Account Manager. Please supply the complete Request & Response payloads. [Warning:] Please remember to NEVER send user login credentials when sending a ticket request. Catch-e staff have our own credentials we can use to de-bug these tickets. |
| 403 - Forbidden | | |
|{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html", "title": "Forbidden", "status": 403, "detail": "Forbidden"}| You do not have permissions for this request. |