Skip to main content
Participant
April 12, 2019
Question

Issues with GetUrlForViewAgreementAssetPage v5

  • April 12, 2019
  • 0 replies
  • 244 views

Hello,

This is from the samples here rest-api-sample/v5/adobesign/api/rest/sample at master · adobe-sign/rest-api-sample · GitHub

The only things that I changed were the OAuth JSON and GetUrlForViewAgreementAssetPage.json

{

  "noChrome": "false",

  "autoLogin": "false",

  "agreementAssetId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

}

I am trying to use this on my website but I keep getting the follow response:

Array

(

  [0] => OAuth Access Token : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  [1] => Unable to process request as URL is found malformed.

  [2] => Unable to process request as URL is found malformed.

  [3] => Failure in getting URL for View Agreement Asset page.

  [4] => java.net.MalformedURLException: no protocol: /views/agreementAssets

  [5] => at java.net.URL.(URL.java:593)
  [6] => at java.net.URL.(URL.java:490)
  [7] => at java.net.URL.(URL.java:439)
  [8] => at adobesign.api.rest.sample.util.RestApiUtils.openConnection(RestApiUtils.java:511)
  [9] => at adobesign.api.rest.sample.util.RestApiUtils.createRequest(RestApiUtils.java:230)
  [10] => at adobesign.api.rest.sample.util.RestApiUtils.makeApiCall(RestApiUtils.java:137)
  [11] => at adobesign.api.rest.sample.util.RestApiViews.getUrlForAgreementAssetViewPage(RestApiViews.java:51)
  [12] => at adobesign.api.rest.sample.GetUrlForViewAgreementAssetPage.run(GetUrlForViewAgreementAssetPage.java:60)
  [13] => at adobesign.api.rest.sample.GetUrlForViewAgreementAssetPage.main(GetUrlForViewAgreementAssetPage.java:41)
)

I have 2 questions that I haven't been able to answer using the forums and documentation:

1. What URL is malformed? Is this the output or the request? I am using java -Xdiag to have better error reporting but it just isn't giving me enough information on this.

2. What is the best way to get the agreementAssetId for the JSON file?

Thank you.

This topic has been closed for replies.