Skribble AG - Notice history

The issue was caused by a configuration problem in our backend services related to our provider. This has now been resolved, and signing with Swisscom AES is functioning normally again.

The root of the issue has been found and we expect to have a fix in the next 60 minutes.

This incident has been resolved with a new deployment at 20:00.

We have identified the issue affecting the "All signatures received" email and have a fix in place. We are currently testing it to ensure everything works as expected before rolling it out. Updates to follow.

Update 11:45 – We have identified and resolved the issue affecting our API.

The problem was introduced with a recent library update, which changed the behavior of resource patching: trailing slashes (/) were no longer automatically accepted.

For example:
✅ GET /v2/signature-requests worked as expected.
❌ GET /v2/signature-requests/ resulted in an error.

Although trailing slashes were never officially documented or required, we found that many integrations relied on this behavior. To restore compatibility, we have now ensured that trailing slashes are accepted for all public resource URLs.

Impact:
Signature requests and other resources created directly or indirectly via the API with trailing slashes may have resulted in broken data since yesterday at 20:00. Unfortunately, this data cannot be fixed and must be recreated by users or APIs.

We sincerely apologize for the inconvenience and appreciate your understanding.