Skip to main content
Participant
November 19, 2015
Answered

Invalid or no file info (INVALID_FILE_INFO) when posting an agreement to EchoSign

  • November 19, 2015
  • 1 reply
  • 2673 views

I'm just getting started with the EchoSign REST API, I've been able to get my tokens and post a transient document, but when I try to post an agreement it's telling me my fileInfo is invalid.

I'm first posting a transient doc, and it's returning the ID, no errors reported, and then I'm passing that into the Agreement, so I'm not sure what it's not liking about my request.

The Response I get is:

Body

{

  "message": "Invalid or no file info is provided",

  "code": "INVALID_FILE_INFO"

}

The fileInfos section of my Request is:

"fileInfos": [{

  "transientDocumentID": "3AAABLblqZhBLgHsD8NRIDaasy5lt2fox0dQ49Z61zp1ctx4twlY2ksuJAT-wKEBtNVQ_0rzBTUEuCJRgyqknbwKJBv1A_lLgV5w1POFYTe7zp4DxAftijwk_Es68idldfbPT_FmEBLri42vyeSIeNq0ptcsZhVhM-hUecAHPy4KgiCeGxzPXinCv5_K5BtIA0Ydh0ssFztw*",

  "documentURL": null,

  "libraryDocumentName": null,

  "libraryDocumentID": null

  }],

I assume I'm missing something simple.

The full request with private information redacted:

Metadata

expect : 100-continue

content-type : application/json

host : secure.na1.echosign.com

access-token : *****

original-path : /rest/v5/agreements

content-length : 1184

accept : application/json, application/xml, text/json, text/x-json, text/javascript, text/xml

method : POST

user-agent : RestSharp/105.0.1.0

accept-encoding : gzip, deflate

requestUrl : rest/latest/agreements

Body

{

     "documentCreationInfo": {

          "signatureType": "ESIGN",

          "formFieldLayerTemplates": null,

          "securityOptions": null,

          "callbackInfo": "www.*****.com",

          "daysUntilSigningDeadline": 7,

          "locale": "en_US",

          "recipientSetInfos": [{

               "recipientSetMemberInfos": [

                    {

                         "securityOptions": null,

                         "fax": null,

                         "email": "IT@*****.com"

                    },

                    {

                         "securityOptions": null,

                         "fax": null,

                         "email": "Jim@*****.com"

                    }

               ],

               "securityOptions": null,

               "recipientSetRole": "SIGNER",

               "signingOrder": null

          }],

          "ccs": ["IT@*****.com"],

          "externalId": null,

          "vaultingInfo": null,

          "signatureFlow": "SENDER_SIGNATURE_NOT_REQUIRED",

          "message": "There is a document ready for you to sign.  Please follow the instructions in this message to digitally sign this document.",

          "formFields": null,

          "mergeFieldInfo": null,

          "fileInfos": [{

               "transientDocumentID": "3AAABLblqZhBLgHsD8NRIDaasy5lt2fox0dQ49Z61zp1ctx4twlY2ksuJAT-wKEBtNVQ_0rzBTUEuCJRgyqknbwKJBv1A_lLgV5w1POFYTe7zp4DxAftijwk_Es68idldfbPT_FmEBLri42vyeSIeNq0ptcsZhVhM-hUecAHPy4KgiCeGxzPXinCv5_K5BtIA0Ydh0ssFztw*",

               "documentURL": null,

               "libraryDocumentName": null,

               "libraryDocumentID": null

          }],

          "postSignOptions": null,

          "reminderFrequency": null,

          "name": "Full Agreement 1"

     },

     "options": null

}

This topic has been closed for replies.
Correct answer jimh29981644

transientDocumentID should be transientDocumentId

save goes for LibraryDocumentID.

You don't want to know how many head-shaped imprints are in my wall thanks to that one.

1 reply

jimh29981644AuthorCorrect answer
Participant
November 20, 2015

transientDocumentID should be transientDocumentId

save goes for LibraryDocumentID.

You don't want to know how many head-shaped imprints are in my wall thanks to that one.