Attestation

Attestation and compliance

Meet legal e-signature requirements for ESIGN, UETA, eIDAS, and country-specific standards like Mexico NOM-151 and Brazil ICP-Brasil

This page covers e-signature compliance. For HIPAA compliance or SOC 2 compliance, see their dedicated pages.

SignatureAPI is legally binding and compliant with US e-signature regulations (ESIGN and UETA), the European eIDAS regulation (at the SES level), and similar laws around the world.

Some countries have additional legal requirements. Use the attestation property to apply a country-specific standard to an envelope.

Available attestations

ValueDescription
noneNo attestation. This is the default and applies to most countries, including the US and EU member states.
mx_nom151Mexico NOM-151 compliance. Attaches a preservation certificate to the deliverable.
br_icp_brasilBrazil ICP-Brasil trusted timestamp. Embeds a timestamp in the deliverable.

Using an attestation

Set the attestation property when creating the envelope:

// POST https://api.signatureapi.com/v1/envelopes
// X-API-Key: key_test_...
// Content-Type: application/json

{
    "title": "Contrato",
    "attestation": "mx_nom151",
    "documents": [
        //...
    ],
    "recipients": [
        //...
    ]
}

Attestations are applied when the envelope completes, as part of generating the deliverable.

Attestations must be enabled for your account before use. Contact support to enable one.