Dear OpenText,
According to the OpenText Product Messaging Service API documentation (https://developer.opentext.com/services/products/messaging-service/apis/messaging-sms-fax-and-email), the endpoint "/faxes/status/" includes the trailing slash "/".
A GET request with a trailing slash to https://t2api.us.cloudmessaging.opentext.com/mra/v1/outbound/emails/status/?job_id=<JOBID> worked without issues about two months ago, but now this request always returns "404 Not Found".
The same GET request works correctly when it is sent without the trailing slash: https://t2api.us.cloudmessaging.opentext.com/mra/v1/outbound/emails/status?job_id=<JOBID>.
The same issue happens with the "/emails/status" endpoint. Earlier, the endpoint worked even with the trailing slash, although the documentation lists it without.
It would be helpful to clarify which version of the URL is correct, because the documentation for "/faxes/status/" includes the slash at the end, while the documentation for "/emails/status" does not.
And for backward compatibility, is it possible to restore support for both options, with and without the trailing slash?
Thank you.
