{"id":3342,"date":"2026-07-06T04:00:58","date_gmt":"2026-07-06T04:00:58","guid":{"rendered":"https:\/\/help.contentsnare.com\/?post_type=ht_kb&p=3342"},"modified":"2026-07-06T05:54:28","modified_gmt":"2026-07-06T05:54:28","slug":"annature","status":"publish","type":"ht_kb","link":"https:\/\/help.contentsnare.com\/knowledge-base\/annature\/","title":{"rendered":"How to Integrate Annature with Content Snare"},"content":{"rendered":"\n

Content Snare’s Annature integration lets you send documents for digital signing directly from your requests. Your clients receive a signing link via email from Annature, and the signed documents are tracked within Content Snare.<\/p>\n\n\n\n

With this integration, you can:<\/p>\n\n\n\n

    \n
  1. Send your request’s PDF export to clients for signing through Annature<\/li>\n\n\n\n
  2. Send uploaded files for signing through Annature<\/li>\n\n\n\n
  3. Optionally lock a request after signing, preventing clients from changing their answers<\/li>\n<\/ol>\n\n\n\n

    Prerequisites<\/h2>\n\n\n\n

    To use the Annature integration, you will need to:<\/p>\n\n\n\n

      \n
    1. Have Administrator<\/strong> level access on your Content Snare account<\/li>\n\n\n\n
    2. Have an Annature<\/strong> account<\/li>\n<\/ol>\n\n\n\n

      Step 1: Get your Annature credentials<\/h2>\n\n\n\n

      Content Snare connects to Annature using three values from your Annature account: an Access ID<\/strong>, an Access Secret<\/strong>, and a Sender Account ID<\/strong>.<\/p>\n\n\n\n

      Create an API key (Access ID and Access Secret)<\/h3>\n\n\n\n

      Log in to Annature and go to Developers<\/strong> in the left-hand menu. In the Keys<\/strong> section, click Create<\/strong>.<\/p>\n\n\n\n

      \"Annature<\/figure>\n\n\n\n

      Give the key a name (for example, “Content Snare”) and click Create<\/strong>.<\/p>\n\n\n\n

      \"Create<\/figure>\n\n\n\n

      Annature will show you the key’s Id<\/strong> and Key<\/strong>. These map to Content Snare as follows:<\/p>\n\n\n\n

        \n
      • Id<\/strong> \u2192 Content Snare’s Access ID<\/strong><\/li>\n\n\n\n
      • Key<\/strong> \u2192 Content Snare’s Access Secret<\/strong><\/li>\n<\/ul>\n\n\n\n

        Copy both somewhere safe. Annature will only show the Key<\/strong> once, so store it securely (for example, in a password manager). If you lose it, you will need to create a new key.<\/p>\n\n\n\n

        \"New<\/figure>\n\n\n\n

        Find your Sender Account ID<\/h3>\n\n\n\n

        Click your profile icon in the top-right corner of Annature and choose My account<\/strong>. Your Account Id<\/strong> is shown at the top of the page. This is your Sender Account ID<\/strong>.<\/p>\n\n\n\n

        \"Annature<\/figure>\n\n\n\n

        About the Sender Account ID:<\/strong> The Sender Account ID determines which Annature account documents are sent from for signing (your Annature envelopes). If you want documents sent from a different Annature account, grab the Account Id from that account instead and enter it here.<\/p>\n\n\n\n

        Step 2: Connect Annature in Content Snare<\/h2>\n\n\n\n

        In Content Snare, navigate to Settings > Applications<\/strong>. Find Annature<\/strong> in the list and click Integrate with Annature<\/strong>.<\/p>\n\n\n\n

        \"Applications<\/figure>\n\n\n\n

        The Configure Annature Integration<\/strong> dialog will ask for the three values from Step 1. Paste in your Access ID<\/strong>, Access Secret<\/strong>, and Sender Account ID<\/strong>, then click Activate<\/strong>.<\/p>\n\n\n\n

        \"Configure<\/figure>\n\n\n\n

        Step 3: Customise the signing email<\/h2>\n\n\n\n

        After activating, you can customise the email that Annature sends to your clients when a document is ready for signing.<\/p>\n\n\n\n

        \"Configure<\/figure>\n\n\n\n
          \n
        • Email Subject<\/strong> – The subject line of the signing request email. Use the Request Name<\/strong> variable to include the name of the request automatically.<\/li>\n\n\n\n
        • Email Body<\/strong> – The body text of the signing email. You can also use the Request Name<\/strong> variable here.<\/li>\n<\/ul>\n\n\n\n

          Click Update<\/strong> to save. You can change these at any time from Settings > Applications<\/strong>.<\/p>\n\n\n\n

          Adding a signature field to a request<\/h2>\n\n\n\n

          Once Annature is connected, you can add signature fields to your requests in the Builder.<\/p>\n\n\n\n

          Enable the external signing integration<\/h3>\n\n\n\n

          When you add or edit a Signature<\/strong> field, you will see the following options in the Field Options<\/strong> panel on the right:<\/p>\n\n\n\n

            \n
          1. Add a Signature<\/strong> field to your request<\/li>\n\n\n\n
          2. Toggle on Enable external integration<\/strong><\/li>\n\n\n\n
          3. Under Signature Integration<\/strong>, select Annature<\/strong><\/li>\n<\/ol>\n\n\n\n
            \"Builder<\/figure>\n\n\n\n

            Choose where signing will be done<\/h3>\n\n\n\n

            Under Where The Signing Will be Done<\/strong>, you have two options:<\/p>\n\n\n\n

            Option A: Signing in the request PDF export<\/strong> The completed request is exported as a PDF and sent to Annature. This is useful when you want the client to sign off on all their answers as a whole.<\/p>\n\n\n\n

            Option B: Signing uploaded files<\/strong> The client uploads files, which are then sent to Annature for signing. Only PDF<\/strong> files are supported when using this option, up to a maximum of 10MB<\/strong>.<\/p>\n\n\n\n

            In both cases, you define exactly where signatures and stamps appear by adding tags to your document (see below). Under What Will Be Signed<\/strong>, choose Sign at specified placements in the document<\/strong>.<\/p>\n\n\n\n

            Setting up signature placements<\/h4>\n\n\n\n

            Your document needs to include special tags where you want signatures and stamps to appear. Annature replaces these tags with the corresponding signing fields before showing the document to your client.<\/p>\n\n\n\n

            Available tags<\/strong><\/p>\n\n\n\n

            Tag<\/th>What it does<\/th>Required?<\/th><\/tr><\/thead>
            STANDARDSIGNTAG<\/code><\/td>Adds a signature placeholder where the client signs<\/td>Required<\/strong><\/td><\/tr>
            SIGNEDDATETAG<\/code><\/td>Automatically stamps the date the document was signed (no client action required)<\/td>Optional<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            Important:<\/strong> Every document must contain at least one STANDARDSIGNTAG<\/code>. Documents without it will be rejected.<\/p>\n\n\n\n

            How to add tags to your document<\/strong><\/h3>\n\n\n\n
              \n
            1. Open your document in Word, Google Docs, or your PDF editor of choice<\/li>\n\n\n\n
            2. Type the tag name (e.g. STANDARDSIGNTAG<\/code>) exactly where you want the signature or stamp to appear<\/li>\n\n\n\n
            3. Change the tag’s text colour to white<\/strong> so it’s hidden against the page background. The tag text is not removed when the signing field is placed, so if you leave it black it will be visible in the final signed document alongside the signing field.<\/li>\n\n\n\n
            4. Save the document and upload it to Content Snare<\/li>\n<\/ol>\n\n\n\n

              Example<\/strong><\/p>\n\n\n\n

              Here’s a document with tags added (shown in black for visibility, but they should be white in your actual document):<\/p>\n\n\n\n

              \"Document<\/figure>\n\n\n\n

              The STANDARDSIGNTAG<\/code> becomes a signature field the client completes. The SIGNEDDATETAG<\/code> becomes an automatic stamp that populates once the document is signed.<\/p>\n\n\n\n

              Lock request on sign (optional)<\/h3>\n\n\n\n

              Toggle on Lock request on sign<\/strong> to lock the request after the client signs. When enabled:<\/p>\n\n\n\n

                \n
              • After the client signs, all other fields in the request are locked and cannot be changed<\/li>\n\n\n\n
              • A banner appears: “Request is Locked – This request is locked because it has been signed.”<\/li>\n\n\n\n
              • The client can click Unlock and revise<\/strong> or the Revise<\/strong> button on any field to make changes, but this will remove the signature and require them to sign again<\/li>\n<\/ul>\n\n\n\n

                This setting is available on both Annature signature fields and Content Snare’s built-in signature fields.<\/p>\n\n\n\n

                What your client sees<\/h2>\n\n\n\n

                Before signing<\/h3>\n\n\n\n

                Your client fills out the request as normal. If the signature field is required, all other required fields must be completed before the client can sign.<\/p>\n\n\n\n

                The signing process<\/h3>\n\n\n\n
                  \n
                1. The client clicks the signature field in the Content Snare request<\/li>\n\n\n\n
                2. Content Snare sends a signing request to Annature, and the client sees “Signing email sent”<\/strong> with the message: “Please check your inbox. We’ve sent a secure link to complete the document signature via Annature.”<\/li>\n<\/ol>\n\n\n\n
                  \"Signing<\/figure>\n\n\n\n
                    \n
                  1. The client receives an email from Annature and clicks Review documents<\/strong><\/li>\n<\/ol>\n\n\n\n
                    \"Annature<\/figure>\n\n\n\n
                      \n
                    1. They confirm consent to sign electronically, then click Review document<\/strong><\/li>\n<\/ol>\n\n\n\n
                      \"\"<\/figure>\n\n\n\n
                        \n
                      1. Annature opens the document. The client clicks Click to begin<\/strong> and is guided to each signing placement<\/li>\n<\/ol>\n\n\n\n
                        \"Document<\/figure>\n\n\n\n
                          \n
                        1. At each STANDARDSIGNTAG<\/code> the client sees a Sign here<\/strong> field. Any SIGNEDDATETAG<\/code> is stamped automatically<\/li>\n<\/ol>\n\n\n\n
                          \"Sign<\/figure>\n\n\n\n
                            \n
                          1. The client adopts a signature (select a style, draw, upload an image, or complete on mobile) and applies it<\/li>\n<\/ol>\n\n\n\n
                            \"Adopt<\/figure>\n\n\n\n
                              \n
                            1. Once signed, Content Snare automatically detects the completed signature and shows “Signing complete!”<\/strong> with the message “All documents have been signed successfully.” The answer is submitted for approval<\/li>\n<\/ol>\n\n\n\n
                              \"Signing<\/figure>\n\n\n\n
                                \n
                              1. If Lock request on sign<\/strong> is enabled, the request locks and a confirmation banner appears<\/li>\n<\/ol>\n\n\n\n

                                If the request is locked<\/h3>\n\n\n\n

                                Once a request is locked after signing:<\/p>\n\n\n\n

                                  \n
                                • The client sees a banner: “Request is Locked – This request is locked because it has been signed.”<\/li>\n\n\n\n
                                • Answers cannot be changed<\/li>\n\n\n\n
                                • To revise any field, the client clicks Revise<\/strong>, which will:\n
                                    \n
                                  • Display a confirmation warning that they will have to sign again<\/li>\n\n\n\n
                                  • Unlock the request<\/li>\n\n\n\n
                                  • Remove the existing signature<\/li>\n\n\n\n
                                  • Allow changes to be made<\/li>\n\n\n\n
                                  • Require the client to go through the signing process again<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

                                    Reviewing signed documents<\/h2>\n\n\n\n

                                    As a team member reviewing the request:<\/p>\n\n\n\n

                                      \n
                                    • You will see “Signing complete!”<\/strong> with the message “All documents have been signed successfully.”<\/li>\n\n\n\n
                                    • A Documents<\/strong> section lists the signed documents with a green Signed<\/strong> badge<\/li>\n\n\n\n
                                    • You can Approve<\/strong> or Reject<\/strong> the signature, just like any other field in Content Snare<\/li>\n\n\n\n
                                    • The locked request banner will note: “This request is locked due to a pending signature. Rejecting a field will unlock it and require the client to re-sign.”<\/li>\n<\/ul>\n\n\n\n

                                      Note:<\/strong> You cannot sign on behalf of your client. When viewing the signature field as a team member, you will see a notice: “You cannot sign this field on behalf of the client.”<\/p>\n\n\n\n

                                      FAQ<\/h2>\n\n\n\n

                                      Can I preview the signing experience as a team member?<\/strong> No. You cannot sign on behalf of your client. The signing email is sent to the client’s email address, so you will need to use a real client email to test the full signing flow.<\/p>\n\n\n\n

                                      Which Annature account do documents get sent from?<\/strong> Whichever account the Sender Account ID<\/strong> belongs to. To send from a different Annature account, copy that account’s Account Id into Settings > Applications<\/strong> and reconnect.<\/p>\n\n\n\n

                                      What happens if my client needs to change an answer after signing?<\/strong> If the signature field locks the request, they can click Revise<\/strong> on any field or Unlock and revise<\/strong> at the top of the request. This unlocks the request and removes the signature, so they will need to sign again after making changes.<\/p>\n\n\n\n

                                      What file types can be signed?<\/strong> When signing uploaded files, only PDF files are supported (up to 10MB). When signing the request PDF export, the export is generated automatically as a PDF.<\/p>\n\n\n\n

                                      My document was rejected. Why?<\/strong> Every document sent to Annature must contain at least one STANDARDSIGNTAG<\/code>. Check that the tag is present and spelled exactly, then re-upload.<\/p>\n\n\n\n

                                      How do I disconnect Annature?<\/strong> Navigate to Settings > Applications<\/strong> and click the Remove<\/strong> button next to Annature.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                      Content Snare’s Annature integration lets you send documents for digital signing directly from your requests. Your clients receive a signing link via email from Annature, and the signed documents are tracked within Content Snare. With this integration, you can: Prerequisites To use the Annature integration, you will need to: Step…<\/p>\n","protected":false},"author":1,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[1040],"ht-kb-tag":[],"class_list":["post-3342","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-integrations"],"_links":{"self":[{"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/ht-kb\/3342","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/comments?post=3342"}],"version-history":[{"count":3,"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/ht-kb\/3342\/revisions"}],"predecessor-version":[{"id":3348,"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/ht-kb\/3342\/revisions\/3348"}],"wp:attachment":[{"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/media?parent=3342"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/ht-kb-category?post=3342"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.contentsnare.com\/wp-json\/wp\/v2\/ht-kb-tag?post=3342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}