Issue Service Credit behavior change

Archived
1

I’ve been using the issue-service-credit endpoint.

Granted, I am still in test mode, so that may have something to do with this behavior, but here is what used to happen when I would use the endpoint to issue a service credit:

{
"errorCode":null,
"errorDetails":null,
"errorMessage":"",
"status":0,
"ReferenceId":"11330"
}

And here is what is happening now:

{
  "errorCode": null,
  "errorDetails": null,
  "errorMessage": "Object reference not set to an instance of an object.",
  "status": 1,
  "ReferenceId": null
}

Has something changed with this endpoint recently? In any case, this error is not super descriptive :slightly_smiling_face: Please help - I need to get this working prior to publishing Roku Billing for our channel.

Thanks!

2

It appears this has been fixed. No longer getting SQL errors from the issue-service-credit endpoint. However, using this even on a paying account, I don’t see a credit in their account. I also made a follow up purchase after the credit and was still charged full price.

Is this endpoint still supported?