0

When I call the enrollment API (configuration/billpay) I'm getting a 404 error. When I use the same userID, but call the payees API, I get results. So clearly the user is enrolled. I can't figure out why I keep getting 404. Can anyone help?

I tried other bill pay related API's and they return results. This one doesn't.

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
Aaron
  • 1
  • Please provide enough code so others can better understand or reproduce the problem. – Community Jul 31 '23 at 10:35
  • Can you update your question with more info such as the `x-request-id` from the response headers? Also, it would be good to see a comparison of the URLs which are being used, to compare the ones that work with the ones that do not. (You can redact specific IDs such as `{userId}` or `{paymentId}`, or `{payeeId}`. It's helpful to follow the Troubleshooting guide as well: https://jackhenry.dev/open-api-docs/troubleshooting/#error-support – Jaime Lopez Jr. Jul 31 '23 at 23:18
  • Here is the URL that fails: https://my.cbna.com/a/consumer/api/v0/users/{UserID}/configuration/billpay x-request-id = 9b3a62d27a1273b350f93fe5de7a3efb Date/Time - 8/1/23 @ 8:10 am est Here is the URL that works https://my.cbna.com/a/consumer/api/v0/users/{UserID}/payees x-request-id = e2bc43b4d30571e4cdcfbd6d21291cd4 Date/Time - 8/1/23 @ 8:12 am est – Aaron Aug 01 '23 at 12:14
  • Thank you. Appears as though we _may_ have a problem with an API Gateway configuration. We'll circle back after conferring with Engineering on this topic. – Jaime Lopez Jr. Aug 01 '23 at 22:44
  • It's indeed a configuration problem with the API Gateway configuration. We expect to have a fix deployed on 08/08/2023. – Jaime Lopez Jr. Aug 04 '23 at 16:58
  • @Aaron, Engineering has deployed a fix and this should now be working again. – Jaime Lopez Jr. Aug 08 '23 at 20:18
  • Ok thanks for the letting me know. – Aaron Aug 09 '23 at 23:37

0 Answers0