If you have questions that are not in the list, do not hesitate to contact us.
The acronym “API” stands for “Application Programming Interface”. An API is an interface used by software components to communicate with each other, for instance when modifying or fetching data. Developers can use the Signere.no API to make applications that interact with Signere.no. In the case of Signere.no, we provide an API method for all functionality in the portal. The programs using the API communicate with Signere.no via the HTTPS protocol.
We have a managed API/code library for .NET that can be downloaded as a NuGet package: https://nuget.org/packages/Unipluss.Sign.Client for .Net 40 and https://nuget.org/packages/Unipluss.Sign.ClientNET35/ for .Net 3.5. This is a wrapper of our REST API, which handles all communication and security internally. For other languages, you can implement HTTP requests and use the REST API directly. If you have a request for a managed API written in another language, please send us an e-mail at teknisk@signere.no
When the user account is created, the keys can be found by logging in to the portal as administrator. In the “Min side” tab, there is a button that displays the API ID (account ID) and the API keys. If you do not yet have an account, see the Get Started section for instructions on how to create one.
The primary key gives access to all resources in the API, specifically creating documents and also administrator privileges like editing the user account. The secondary key gives access to day-to-day services like getting documents, viewing statistics and so on.
We support JSON and XML. In the HTTP Accept header, specify which format you want to use. For instance, if you want to use XML, the header reads Accept: application/xml If the format is not provided, the default server format is JSON.
The keys that are issued when the API account is created (the primary and secondary keys) are utilized to produce a token. Almost all services in the API require this token. If the provided token is not correct, the server will reject the request. For more information about the API security and how to generate the token, click here.
The REST API uses some headers to provide the timestamp, the API token etc. See the documentation for more information.
For the moment we only have a REST API and a managed .NET API. There are several reasons that motivate our choice of making a REST API instead of a SOAP API. One important reason is that most operations are purely stateless (like create, read and update) and are therefore suited for caching. REST reads can be cached, while SOAP reads cannot. Furthermore, REST permits JSON content, which parses faster. In general, REST has better performance and scalability than SOAP.
The documents are stored in two independent data centers: Microsoft and Amazon Web Services. We use geo-redundant storage with both providers to ensure maximal availability in case of technical problems at the data centers. We offer storage on Norwegian soil as an extra service. If you wish to order this or have further questions, contact at salg@signere.no.
Yes, the API supports multiple signatures per document, When you use multiple signatures, the document is not signed before all the recipients have signed. Also be aware that there is an additional charge pr extra signature, for prices contact sales at salg@signere.no.