Pre-production testing

The new version of Signi is good news, new features will be available and therefore a new opportunity to streamline processes. If you are waiting for a new feature, you will welcome the opportunity to test it and give us feedback before it goes live. At the same time, a new release risks "breaking" something that has worked before. Which is a situation we all want to avoid.

That's why we give users who have subscribed to Signi Extended Support, are running a major implementation project with planned new features, or are developing partner solutions the opportunity to verify that the existing and new versions are working properly before releasing a new version.

If you are interested in Extended Signi Support, please contact us at [email protected].

Attention!!! - The pre-production environment https://app.pre.signi.tech/ is independent of the production environment http://app.signi.com. Therefore you need to create an account there again, under the same , typically company email. In terms of behavior, these are completely different services like Rohlik.cz and Amazon.com.

Common test workspace

When to use it

• You need to "click through" new functionality without spending too much time preparing the environment for your test scenario.

• You'll have a workspace that has everything you need to execute different test scenarios. For example, for HR there are employees who have a Signi account and are drafters and employees who do not have a Signi account and sign as counterparties see below.

Examples of test users - proponents or opposing parties, emails to all go to the [email protected] email group, where those interested in texting can also be added.

What needs to be done

• We will invite you to the DEMO CZ PRE workspace at https://app.pre.signi.tech/. 

• At the same time, we will add your email to the [email protected] email group, i.e. you will receive notifications for all team members and contacts of this workspace, and you will be able to play the role of everyone listed in your signature scenario.

How to test integrations

• Simple. Just use the API key for workspace DEMO CZ PRE at https://app.pre.signi.tech/, which is  eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJpYXQiOjE2NzYxNDQwMjAsImV4cCI6MTY3NjE0NzYyMCwicm9sZXMiOlsiUk9MRV9GUk9OVEVORF9BUEkiXSwidXNlcm5hbWUiOiJkZW1vQHNpZ25pLmNvbSJ9.PHxZbWdGlRma883QLFu3ObJaQIiLyAyQBqppxKBIdbUulptqvCYcfVELMN_SQRsHGgJOa7lQZEBs168-vJJAWrnt_9ez6

• At the same time, you can use any examples from the JSON sample library, you just need to:

  • specify https://api.signi.com/api/v1/… as the endpoint address instead of https://api.pre.signi.tech/api/v1/…

  • edit the emails from the examples from [email protected] to [email protected],

  • use the API key above.

Own test workspace 

When to use it

• We have more complex signature scenarios and you need to set up the environment entirely on your own.

• In integrations where you want to redirect the test environment to Signi pre-production at certain points to verify that existing functionality is preserved.

What you need to do

• Create your main Signi account at https://app.pre.signi.tech/ as you would when onboarding on a cloud instance of Signi app.signi.com. Together we will then go through a shortened administrative onboarding where we will create a workspace, set up the necessary features on it, generate API keys, add credits, etc.

Recommendations to increase efficiency / simplify life:
Create a pre-production account under your main Signi.com account i.e. [email protected].	
Create a workspace named DEMO - <your company>.	
Invite users of [email protected], to your workspace so that we can look at your data and advise you faster.

How to test integrations

• Simple. As part of Onboarding, an API key is generated for your dedicated workspace for Signi pre-production.

• At the same time, you can use any examples from the JSON sample library, you just need to:

  • specify https://api.signi.com/api/v1/… as the endpoint address instead of https://api.pre.signi.tech/api/v1/…

  • modify the emails from the examples from [email protected] to your users,

  • use the API key generated as part of your onboarding.