Electronic signatures in API mode

With an electronic signature you:

• Guarantee the integrity of an electronic document
• Identify the author, by analogy with the handwritten signature on a paper document
• Assure non-repudiation, the signee cannot deny having signed the document

An electronic signature responds to the following demands:

• Is unique to the signee
• Is created in a way in which the signee can maintain exclusive control
• Guarantee a link to the act to which it is attached

By signing up to the API offer, you have complete access to the API catalogue of electronic signatures, where you will find documentation about all exposed webservices as well as a test area so that you can experiment with different webservice calls and test your pathways fully before integrating the webservices into your IS, business application or website.

Support is included in the API offer to guide you with the integration. Nevertheless, complementary services are also available in case you want further support. Contact our team for more information.

With Docaposte's APIs, you can electronically sign the following document formats:

• PAdES : PDF Advanced Electronic Signature 

1. the norm ETSI TS 102 778 (parts 1 to 5) 
2. allows you to sign documents in PDF format
3. and is highly adapted to dematerialization of invoices, orders, etc.
4. The Reader (usually Abode Reader) includes signature verification (the famous signature panel, accessible on the blue line at the top of a signed PDF)

• XAdES: XML Advanced Electronic Signature

1. All XML-DSig (ETSI TS 101 903) norm extensions which make it compatible with advanced electronic signatures
2. Allows you to sign documents in XML format
3. The interest of this format is that you can sign parts of the document, without breaking the signature of another part signed by another signee
4. Widely used by the French administration
5. It is also used by Microsoft Office (from 2010)

• CAdES: CMS Advanced Electronic Signature

1. A range of extensions to the Cryptographic Message Syntax (CMS) signature standard making it compatible with advanced electronic signatures (ETSI TS 101 733)
2. Allows signing of CMS or S/MIME (e-mails) binary files
3. Especially adapted to binary content as it does not require transformation (for example: videos, images, programs, etc.)
4. Presents the benefit of natively managing cosignatures of the same level

With our identity verification services, our APIs offer the possibility to produce advanced signatures in your signature pathways. These services can be activated at the start of the project.