Public API: Envelope requests containing NULL as the party_ID produce an error 400

Update timeline

1. resolved Dec 12, 2022, 02:59 PM UTC

   Thanks for your patience whilst we rectified the issue last week, to give you a little more information about what happened and how we will prevent it from happening in the future, here is the breakdown. ## What happened? Between the hours of 11:20 am and 12:20 pm on Wednesday, 7th Dec 2022, a subset of Signable API users encountered a 400 error when sending envelopes. The event was triggered by a change first deployed at 11:20 am, intended to fix a bug in how the public API treats duplicate party ID’s being sent in the same request. The fix did not take into account the use case where party ID’s were set to NULL, and so these requests failed. The issue was detected within a few minutes of deploying, and the team immediately proceeded to revert the code changes to get the system back to its original state. ## What are we doing about this? We’ve amended the code and unit tests to account for cases where the party ID is set to NULL and have redeployed the fix. If you need any more information, get in touch at [email protected].