Introduction
We're excited to announce the release of Zigned REST API version 3.2.4. This update introduces the ability to forward participants.
How does it work?
It's extremely simple. Just send a POST Request to agreements/<id>/participants/<id>/forward with the following payload:
{
"forward_to_email": "<email>"
}
...and that's it! The new participant will receive an invitation and we will take care of the rest behind the scenes. If you need to subscribe to these changes, we'll fire off a participant.draft.update event.
Why is forwarding such as big deal?
It can seem quite trivial, but in our commitment to delivering a transparent, simple and powerful e-signing solution we always take care to make sure that each event surroding the signing process is documented and accounted for. That's why even simple things such as forwarding an invitation, needs to ensure that your documents and signing processes are as tight as they can be.
Get started
To get started, log in to your account and navigate to the API client settings on zigned.se. From there, you can upgrade your client to version 3.2.4.
These updates are part of our commitment to providing a robust and flexible e-signing solution. We encourage you to explore these new features and see how they can improve your workflows and digital agreement management.
For detailed documentation and more information on how to implement these new features, please visit our API documentation page.
Stay tuned for more updates as we continue to enhance our services to better serve you!