For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dropbox Sign WebSDKsSign Up
DocumentationAPIChangelog
DocumentationAPIChangelog
    • Overview
  • Guides
    • API Dashboard
    • API Settings
    • SMS Tools
      • NOM 151 Overview
      • Implementation
    • Reports
    • Fax
  • SDKs
    • Overview
    • Versioning Policy
  • Walkthroughs
    • Non-Embedded Signing
    • Text Tags
    • Templates
    • Embedded Signing
    • Embedded Templates
    • Embedded Requesting
  • Additional Resources
    • Embedded Testing Tool
    • API Help Center
LogoLogo
Dropbox Sign WebSDKsSign Up
On this page
  • What is NOM 151?
  • How does NOM 151 work?
  • How can I add NOM 151 to my workflows?
  • Setup
GuidesSignature Types

NOM 151 Overview

||View as Markdown|
Was this page helpful?
Previous

Using eID

Next

Implementation

Built with

What is NOM 151?

NOM 151, or Normativa 151, is a Mexican standard that guarantees the integrity of electronic documents. It provides a data retention certificate that verifies the document hasn’t been altered after signing, confirming its integrity and reliability for any transaction.

How does NOM 151 work?

Dropbox Sign integrates with eID Easy, a partner of Edicom, to support NOM 151 compliance for both Dropbox Sign web and API users in Mexico. This integration creates a secondary certificate, separate from the original signed document, that verifies its integrity according to NOM 151 regulations.

With the NOM 151 certificate enabled, signature requests will have this secondary certificate added to the request, which can be accessed through your Dropbox Sign account once the request is completed.

How can I add NOM 151 to my workflows?

Dropbox Sign users on a Premium plan can enable this feature through their Admin Console settings. Admins can navigate to their “Signature request options” settings to enable the NOM 151 certificate feature for their signature requests. Once enabled, the option to add a NOM 151 certificate will appear as an additional checkbox under the Signature Type options in the Dropbox Sign web workflow. Additionally, API users will be able to include the nom_151:true option in the certification_types parameter.

Setup

Note: You must have a Dropbox Sign Premium plan to use NOM 151. Please see out our Dropbox Sign Pricing and our API Plans and Pricing page for more information.

StepsImages
1. Open the Admin Console from the user menu in the Dropbox Sign web page.Image of Admin Console navigation link in settings
2. In the Admin Console, select “Settings” and then “Signature requests”. Scroll to the “Signature request options” subsection and navigate to the NOM 151 entry.Image of NOM 151 option in Admin Console
3. Activate NOM 151 by selecting the switch control.Image of enabling NOM 151 option
4. Select the “Save settings” button. If activation is successful, you’ll see a green banner with a confirmation appear at the top of the screen.Image of successful enablement notification