API limits have since a number of years supplied the API config limits from the API directly. We should just go through the API catalogue and see if there are any APIs that doesn't supply the config information. If not, remove them from the API catalogue and the unit tests/ping of APIs to limit the maintenance workload.
Also generate message to send to api when there are errors.
Also add email as a slot for each PXWEB api to prepare messages with error messages.
API limits have since a number of years supplied the API config limits from the API directly. We should just go through the API catalogue and see if there are any APIs that doesn't supply the config information. If not, remove them from the API catalogue and the unit tests/ping of APIs to limit the maintenance workload.
Also generate message to send to api when there are errors.
Also add email as a slot for each PXWEB api to prepare messages with error messages.