PageSize and page reverting to default on some end points

I am have some trouble with the querying payments and invoice end points, the pageSize and page keep reverting to the defaults on the following endpoints:

GET https://provider.api-compliance.acc.co.nz/api/v1/claims/vendors/invoice/{scheduleId}

GET https://provider.api-compliance.acc.co.nz/api/v1/claims/vendors/payments/details/{paymentReference}

eg.

 

GET https://provider.api-compliance.acc.co.nz/api/v1/claims/vendors/invoice/{scheduleId}

request: outgoing-126 >> "GET /api/v1/claims/vendors/invoice/8_______?vendorId=Z______&pageSize=5&page=1 HTTP/1.1[\r][\n]"

response: http-outgoing-126 << "{"message":"Success","generatedAt":"2018-10-12","pageSize":25,"totalPages":1,"page":1,"invoiceStatusDetailsList"

 

GET https://provider.api-compliance.acc.co.nz/api/v1/claims/vendors/payments/details/{paymentReference}

request:: http-outgoing-8 >> GET /api/v1/claims/vendors/payments/details/143_____?vendorId=G____&pageSize=25&page=3 HTTP/1.1

response http-outgoing-8 << "{"message":"Success","generatedAt":"2018-10-12","pageSize":25,"totalPages":3,"page":1,"invoicePaymentAdviceDetailsList":[

 

Where as the following endpoint works fine:

GET /api/v1/claims/vendors/submissions

2018-10-12 17:22:40.362 DEBUG 3206 --- [nio-8080-exec-6] o.a.h.wire : http-outgoing-124 >> "GET /api/v1/claims/vendors/submissions?vendorId=XXXXX&startDate=2018-09-24&endDate=2018-09-30&pageSize=5&page=2 HTTP/1.1[\r][\n]"

2018-10-12 17:22:41.113 DEBUG 3206 --- [nio-8080-exec-6] o.a.h.wire : http-outgoing-124 << "{"message":"Success","generatedAt":"2018-10-12","pageSize":5,"totalPages":3,"page":2,"invoiceSubmissionList"

Any ideas what is happening here?

Thanks

Hi Clarke:

 

That's an exist known issue for our v1 APIs, but we are fixed this issue in our last release which is v2. So can you please try those two endpoints:

GET https://provider.api-compliance.acc.co.nz/api/v2/claims/vendors/invoice/{scheduleId}

GET https://provider.api-compliance.acc.co.nz/api/v2/claims/vendors/payments/details/{paymentReference}

 

Please let us know if the issue still exists.

 

Leon


Thanks, I will start moving over to v2