Issue with PUT call only on Sandbox
Tuesday, February 27, 2024 at 10:54amGuys,
I am getting this error when trying to update the package status of a package. Is there something going on with the PUT call? I am able to do the other POST calls.
url - https://sandbox.esignlive.com/api/packages/{transactionID}
{StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
Connection: keep-alive
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=A5EhVQdCy%2BgSs8JSdqrmkWWFAPMYnm4FovuRzjuOHhDXTf1eia4G2DDZ6WKT2KYFItyNN7%2FhVXOqV%2FzpdNRpHYaRGAIXgo4LgX0Y1n7cLUvfbNpT0Et9x%2B%2BIRRJhhLimrySxbQjtWQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
X-Content-Type-Options: nosniff
CF-RAY: 85c1a8580f5b4678-DFW
Date: Tue, 27 Feb 2024 16:03:23 GMT
Server: cloudflare
Content-Length: 183
Content-Type: application/json
}}
Note: This call has been working since the beginning of time and we haven't made any changes to our calls in a while.
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 08:55amHi Ryan,
Thanks for bringing it to us! Is your application using .NET sdk or REST API to invoke the PUT call? May I have an example transaction ID and the payload you were using? Also, could you also fill in a support ticket to report this if the issue is reproducable?
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 09:45amDuo,
I am using the REST API to invoke the PUT call. Here is an example transaciton ID where I am getting the above error.
JPiRZRI6DXnCOOcH20ciq_Y4D2c=
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 10:15amDuo -
After digging into this error on my side I am getting this error.
"Notary signer has to be an account sender."
Did something change here recently?
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 10:36amHi Ryan,
As far as I am aware, a notary signer is required to have an OSS sender profile, which remains unchanged. For this transaction, your email ([email protected]) is already specified as the notary (notaryRoleId: e98ddfa4-c6c1-4c76-9e35-19daf577d547). Were you trying to switch the notary to another signer?
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 10:38amDuo,
No, I was trying to put the package into SENT status. It was currently in DRAFT status from just being created. I looked over the JSON package that I sent to get this package created and everything looks fine on this end so I am left confused but this is happening on all Notary transactions in our test environment.
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 10:42amI see, let me reproduce a similar transaction and will update you if I found anything.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 10:45amHi Ryan,
I can reproduce the issue. I'd like to raise a support ticket on your behalf and report this to support team. We can continue the discussion from there.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Issue with PUT call only on Sandbox
Wednesday, February 28, 2024 at 10:46amPlease do and keep me informed. I am glad that you were able to reproduce the issue.