Skip to main content

6 posts tagged with "v3"

View All Tags

· 3 min read
David Jurio

Introduction​

We're thrilled to announce the release of Zigned REST API version 3.2.5. This update introduces a new resource: Observers. Let's dive in to what they are and how they can help you manage your agreements.

What are Observers?​

Observers are passive participants in a signing process. Depending on their scope, they can have access to the signing room and follow the process or just receive a copy of the signed document once it's completed. This can be useful for stakeholders who need to be kept in the loop but don't need to actively participate in the signing process.

How does it work?​

Observers are subresource for agreements, so all you need to do is send a POST Request to agreements/<id>/observers with the following payload:

{
    "observer_scope": <"viewer" | "cc">,
    "email": "<email for the observer>",
    "name": "<name of the observer>"
}

You need to specify at least one of the fields email or name. If the observer_scope is set to "cc", or the agreement has communicaton enabled, an email is required.

Difference in scopes​

  • viewer: The observer will have access to the signing room and can follow the process, besides receiving a copy of the signed document.
  • cc: The observer will only receive a copy of the signed document once the process is completed. The observer will not have access to the signing room.

Use cases​

  • Viewer: Useful for stakeholders who need to follow the signing process but don't need to actively participate. For example, a project manager who needs to keep track of the progress of a contract.
  • CC: Useful for stakeholders who need to receive a copy of the signed document but don't need to follow the signing process. For example, a legal department that needs to keep a copy of all signed contracts.

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.5.

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!

· 2 min read
David Jurio

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!

· 4 min read
David Jurio

Hi there!​

We're excited to announce the release of Zigned REST API version 3.2.3. This update introduces the ability to gather qualified signatures, in cooperation with ZealID.

About Qualified signatures​

Qualified signatures hold the same legal weight as handwritten signatures, and are recognized in the EU and EEA. This makes them ideal for contracts and agreements that require a higher level of security and legal certainty. Some governments and organizations (such as Bolagsverket in Sweden) even require it for certain types of documents. By utilizing ZealID's qualified signatures, you can ensure that your agreements are legally binding and secure.

How does it work?​

From a users perspective it is not that much different from signing with common digital ID:s. Below we detail the process in broad steps:

1. Creating their ZealID​

The user must first create their ZealID account by downloading the app from the Apple Appstore or Google Playstore. While registering is a quick one-time process, it requires the user to have a physical ID, such as a passport, at hand.

2. Initiating the signature process​

When initiating the signing process via zigned.se, the user will be prompted to authenticate with ZealID. After the authentication is completed, they are directed back to Zigned to complete their signature.

3. Signing the document​

When the user is ready, they sign the document by scanning a QR-code with the ZealID app. The app will then prompt the user to confirm the signature, and the signature is processed by us.

Get started with Qualified signatures​

In order to get started with qualified signatures, you need to upgrade your API client to version 3.2.3 or higher. You can do this by navigating to the client settings on zigned.se and selecting "Upgrade".

Caveats and limitations when using Qualified signatures​

We embed your qualified signature as a native PDF signature. As such, it is limited to the same restrictions as any other PDF signature:

  • The signing process must be sequential, as each signature builds on the previous.
  • Since the signature is embedded in the PDF and the process is sequential, it is not possible to combine with detached signing methods such as BankID.
  • Parallell signature workflows, such as the use of signing groups, are not supported as it goes against the PDF standard.

So why use it?​

Qualified signatures hold the same legal weight as handwritten signatures, and are recognized in the EU and EEA. This makes them ideal for contracts and agreements that require a higher level of security and legal certainty. You can combine it with other signature workflows and processes and only use it to certify the process at the end.

The future of qualified signatures and Zigned​

We are excited to be the first provider in Sweden to offert qualified signatures with a pay-per-use model. We have plans to further integrate it with our other signature offerings (such as advanced signatures) for smooth integrations and workflows. If you have suggestions, feedback or requests, please contact us.

About ZealID​

ZealiD is a Qualified Trusted Service Provider specializing in issuing Qualified Electronic Signatures. ZealiD Qualified Electronic Signatures are recognized within the EU Member States as legally binding. In addition, ZealiD is certified as a Registration Authority, meaning that they provide remote identification services. Curious? Learn more about ZealID here

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!

· 2 min read
David Jurio

Hey everyone​

We’re excited to roll out the latest update to our platform, Version 3.2.2, available as of today, June 18, 2024. This update introduces some powerful features designed to streamline your workflow and enhance usability.

What’s New?​

  1. Batch Participant Addition: You can now add multiple participants at once through the new participants/batch endpoint. This feature aims to save time and reduce the effort needed when setting up documents that require multiple signatories. Check out our API reference for detailed instructions on how to implement this in your setup.

  2. Automated Role Assignment: To simplify the process further, if the email of a specified issuer matches that of a participant, and it’s unique to them, we’ll automatically assign them as a 'signer' or 'approver'. This eliminates the need for manual role specification in many common cases.

  3. Relaxed Issuer Requirements: For those acting merely as observers, specifying an email address for an issuer is no longer necessary. This should help reduce the clutter and focus on what’s really needed for active participants.

How to Upgrade?​

To start using these new features, you’ll need to opt-in by upgrading your API client. Simply head over to your API client settings on zigned.se and click "Upgrade".

We hope you find these updates helpful! As always, we’re here to support you, so if you have any questions or need assistance, feel free to reach out.

Happy signing!

· 2 min read
David Jurio

Hi there!​

We're excited to announce the release of Zigned REST API version 3.1.1. This update introduces several new features and improvements, enhancing our platform's functionality and flexibility. Here's what you need to know:

Default Locale Specification​

You can now set a default locale for an agreement. As of now, Swedish and US English is supported with more languages to be added in the future. Users can always set their preferred language once they visit their signing room.

Truid Signature Method​

We've integrated Truid as a signature method to provide advanced signature capabilities globally. Truid enables compliant electronic signatures across various jurisdictions, ensuring that you can collect signatures with strong identity verification outside of Sweden as well. Learn more about Truid and its availability.

API Client Version Lock​

API Clients are now tied to the version available at their creation date. Changes made to the API's response structure are opt-in, ensuring backward compatibility and smoother transitions for existing integrations. To adapt to the latest API changes, users can upgrade their client by navigating to the client settings on zigned.se and selecting "Upgrade". This feature allows users to control when they adopt new changes, providing flexibility and maintaining stability across different client environments.

New Webhook Scope​

The new client scope for Webhooks allows notifications to be limited to actions triggered by a specified API client, enhancing control over webhook management and ensuring Webhook data is locked to the same version as the API Client.

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!

· 2 min read
David Jurio

Hello, digital innovators!​

We're excited to introduce a significant update to the Zigned REST API. Incorporate the full suite of Zigned's e-signing features directly into your own systems. Let's explore the fusion of flexibility and functionality that our REST API brings to your digital doorstep.

Embracing Flexibility and Control with Zigned's REST API​

Our latest REST API is a testament to our commitment to providing versatile and user-driven solutions. It's designed not only to enhance your e-signing processes but also to embed seamlessly into your existing workflows.

A User-Centric Approach​

We believe in making technology accessible and user-friendly. Our REST API is designed with you in mind – focusing on clarity, ease of use, and a commitment to providing excellent support.

Exciting New Features Awaiting You​

  • Self-Directed Communication: You now have the power to manage participant notifications. Choose when and how to communicate, aligning perfectly with your operational style.

  • Callback URLs for Enhanced Workflows: Integrate Zigned more deeply into your workflows with Callback URLs. Redirect participants to any URL post-signing, making Zigned a dynamic part of your larger ecosystem.

  • Pause and Edit Capabilities: Gain greater control over your agreements with the ability to pause the signing process and edit details. This feature brings unprecedented flexibility to your document management.

  • Webhooks for Real-Time Updates: Stay informed with real-time notifications. Our webhooks let you know the moment any significant event occurs in your e-signing process.

Get Started with Ease​

Dive into our comprehensive documentation, complete with examples and clear explanations. Whether you’re a seasoned developer or just starting, our API is built to empower you to achieve more with less hassle.

Your Feedback Matters​

Your journey with our REST API is important to us. We’re always here to listen to your feedback, suggestions, and ideas. Let’s grow and improve together!

Join Us on This Exciting Journey​

We’re just getting started, and the possibilities are endless. Stay tuned for updates, new features, and even more ways to enhance your e-signing experience.

Thank you for choosing us as your partner in digital transformation. Let's make e-signing simple, secure, and efficient together!