You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where {urlPrefix} is "api.cybersource.com" or "apitest.cybersource.com", and {startTime}/{endTime} are ISO 8601 timestamps like "2017-10-01T10:10:10+05:00"
Since these two endpoints have different parameters and URIs than the regular report downloads (/reporting/v3/report-downloads) in lib/Api/ReportDownloadsApi.php, that one cannot be used.
I kept trying to use ReportDownloadsApi.php mistakenly and kept getting a resource not found error. The Servlet to REST API Migration Guide says the Chargeback reports are retired.
However, I eventually tracked down a PDF called Reporting_API_WellsFargoPaymentGateway.pdf that reveals they are not in fact retired, and gives the required URI and parameters.
I think it would be very helpful to include API classes for Chargeback Details and Summaries reports.
The text was updated successfully, but these errors were encountered:
In lib/Api/, there are no APIs provided for the following:
startTime={startTime}&endTime={endTime}
startTime={startTime}&endTime={endTime}
Where {urlPrefix} is "api.cybersource.com" or "apitest.cybersource.com", and {startTime}/{endTime} are ISO 8601 timestamps like "2017-10-01T10:10:10+05:00"
Since these two endpoints have different parameters and URIs than the regular report downloads (/reporting/v3/report-downloads) in lib/Api/ReportDownloadsApi.php, that one cannot be used.
I kept trying to use ReportDownloadsApi.php mistakenly and kept getting a resource not found error. The Servlet to REST API Migration Guide says the Chargeback reports are retired.
However, I eventually tracked down a PDF called Reporting_API_WellsFargoPaymentGateway.pdf that reveals they are not in fact retired, and gives the required URI and parameters.
I think it would be very helpful to include API classes for Chargeback Details and Summaries reports.
The text was updated successfully, but these errors were encountered: