Getting Started — inSign Electronic Signature API (eIDAS)

1

Create Session

POST /configure/session

Upload a document and create a signing session. The response contains a sessionid.
You can provide your PDF in several ways: as a public fileURL (used below), as a Base64-encoded string via fileB64, or as a multipart/form-data upload. For details see the API Explorer.

Request Body

Response

2

Invite Others to Sign

POST /extern/beginmulti

Invite external participants to sign the document. Each signer is assigned a role matching the signature fields in the PDF.
You control how signers access the session: set sendEmails: true to have inSign send invitation emails automatically, or use singleSignOnEnabled: true to get back a direct URL you can embed in your own app or workflow. Signers can be added inOrder (sequential signing) or all at once (parallel). Each signer only sees the fields assigned to their role.

Request Body

Response

3

Check Status

POST /get/status

Poll the session status to see signing progress, document metadata, and signature field details.

Request Body

Response

4

Download Document

POST /get/document

Download the signed PDF. Parameters are passed as query string.

Query Parameters (as JSON)

Response

Ready for the full experience?

Great! You created your first session!

Signing links are ready!

You just signed your first document!

inSign API - Getting Started

Status of your current session

Create Session

Invite Others to Sign

Check Status

Download Document

That's the core flow

cURL Command

Ready for the full experience?

Great! You created your first session!

Signing links are ready!

You just signed your first document!

inSign API - Getting Started

Status of your current session

Create Session

Invite Others to Sign

Check Status

Download Document

That's the core flow