Create signature request

On creating signature requests, the following fields can be specified:

Field	Direct flow		Portal flow	Extra information
Documents	Mandatory		Mandatory	1-20 documents [4]
Signer(s)	Mandatory		Mandatory	see Addressing signers
Title	Mandatory		Mandatory	Maximum 80 characters [1]
Non-sensitive title / Description	Not applicable		Optional	Maximum 80 characters [1]
Signature type	Optional		Optional	see Signature type
Security level	Optional		Optional	see Security level
Message to receiver(s)	Optional		Optional	Maximum 220 characters [1]
Signer identifier	Optional		Optional	see Addressing signers
Activation time	Cannot be overrided [2] | Optional
Lifetime	Cannot be overrided [3] | Optional
E-mail address	Not applicable		Mandatory	see Notifications and contact details
Mobile number	Not applicable		Optional	see Notifications and contact details
Sequence	Not applicable		Optional	see Chained signing

Footnotes

[1] (1,2,3)

The maximum number of characters permitted is valid in both direct and portal flow.

[2]

Signature requests in direct flow are always activated immediately after creation. The default value is immediately after creation.

[3]

Signature requests in direct flow always have a 30-day lifespan, to avoid a document being signed far too long after the creation of the task. Any deadline from the sender’s perspective must be communicated and handled in the sender’s services.

[4]

Multiple documents are not supported for advanced signature from public organizations

For implementation of signature requests in portal flow, see Portal flow, and for signature requests in direct flow, see Direct flow.

Limitations

Number of signers

A signature request may have several signers. The service allows a maximum of ten signers per request.

Speed

The service permits a maximum of 10 API calls per second per organization number. If a sender exceeds this limit, the API will return HTTP 429 Too Many Requests, and the sender will be blocked for 30 seconds.

Document format

The service supports PDF (.pdf). documents. Both PDF and PDF/A are by the service. The signed document will be of the same type as the original documents. One or more original documents that are PDF/A give a signed PAdES document that is PDF/A, and one or more original documents that are PDF version 1.1-1.7 give a signed PAdES document that is PDF version 1.7. If the original documents contain both PDF and PDF/A, the signed document will be of the PDF version 1.7 type. For PDF/A, the service will always produce signed PAdES documents of the PDF/A-3b type, irrespective of the PDF/A version and conformity level of the original documents.

For archiving of signed documents, we recommend using original PDF/A documents. This is a requirement if the signed document is to be submitted to the National Archives of Norway.

For testing, use the example documents PDF-1.2, PDF-1.3, PDF-1.4, PDF-1.5, PDF-1.6 og PDF-A.

Note

The documents can amount to maximum 10 MB (10 485 760 bytes) in size. PDF versions supported are PDF 1.1-1.7.

In PAdES, the documents will always be presented in A4 and portrait format. For best results, it is recommended that the submitted documents are also in this format.

Caution

Password-protected documents (restricted reading and/or writing access) are not supported by the service.

Activation time

Indicates the time when the signature request is to be made available to the signer(s). If the activation time is in the past, the reuqest will be available immediately after creation.

Signature requests in direct flow are always activated immediately after creation.

Lifetime of the request

Indicates for how long after activation a signature request is available to the signer before it expires. Can be maximum 90 days after activation.

Signature requests in direct flow always have a 30-day lifespan, to avoid documents being signed far too long time after the creation of the request. Any deadline from the sender’s perspective must be communicated and handled in the sender’s services.