IduraDocumentation
  1. Signatures
  2. Getting Started
  3. Set up the Dashboard

Before you build with the Signatures API, you need to configure your environment in the Idura Dashboard. It takes about two minutes and gives you the client credentials for calling the Signatures API.

Create a tenant

A tenant represents your organization’s isolated environment at Idura.

  1. Sign up for a free test account to access the Idura Dashboard.
  2. You will be prompted to create your first tenant. You can change the tenant name at any time after creation in the Dashboard Settings.

Risk-free testing: your free account includes a sandbox with unlimited test signature orders, so you can build and test without any cost or commitment.

Register a domain

Every signing request runs through your Idura domain.

  1. Go to the Domains tab in your Dashboard.
  2. Click Register domain.
  3. Choose a domain type. For local development, start with a .test.idura.broker domain.
  4. Type your domain name in the Domain settings field. For a company called Acme Corp, a first domain might be acme-corp.test.idura.broker.

Create a Signatures application

An application represents the backend service you are building, for example your Node.js or C# service that creates signature orders. Creating an application generates the client credentials you’ll need to call the Signatures API.

  1. Create a new Signatures application from the Applications tab of your Dashboard.
  2. Configure your application:
  • Name: Choose a recognizable name.
  • Domain: Select the domain you registered above.
  • Client ID / Realm: Use the auto-generated identifier (for example urn:my:application:identifier:123) or set your own.
  • eID providers: Select eIDs you want to support.
  • Technology: Select the option that matches your stack, for example Node.js, C#, or Java.

You’ll be able to update your application settings later.

  1. Click Create Application.

Your client ID and client secret will appear in a popup. Copy and save them in a secure location, then use them in your code to integrate with the Signatures API.

Client ID and Secret for a Signatures Application

Lost your client secret?

Idura stores the client secret as a hash, so once you close the popup you cannot read it again. If you lose it, create a new client ID and secret pair from the API section of your application settings, then update both values in your code.

Signatures Application settings

What’s next?

Your Dashboard is configured and your API credentials are ready.

To test document signing, you need to create a test user for the eID(s) you’re planning to use. Note that you can’t use your real, personal eID in a Test environment.

Ready to test? Create your first test user.