Skip to main content
chaozheng_7571
Participant
May 26, 2026

Agreement state is OUT_FOR_SIGNATURE but signingUrls API returns AGREEMENT_NOT_EXPOSED error

  • May 26, 2026
  • 3 replies
  • 24 views

I am using the Adobe Sign REST API (v6). I have an agreement whose status is OUT_FOR_SIGNATURE. However, when I call the /agreements/{agreementId}/signingUrls endpoint, I receive the following error:json

 

{
"code": "AGREEMENT_NOT_EXPOSED",
"message": "Agreement is not exposed for signing"
}

According to the documentation, agreements in OUT_FOR_SIGNATURE state should be available for signing and the signing URLs endpoint should work.Questions:

  1. Why would an agreement be in OUT_FOR_SIGNATURE but still return AGREEMENT_NOT_EXPOSED?
  2. Are there any additional conditions or prerequisites (e.g., participant roles, workflow type, authentication method, or agreement settings) that must be met before signingUrls can be retrieved?
  3. What is the recommended way to handle or resolve this?

apiAccessPoint is https://api.na3.adobesign.com/, for test

3 replies

John T Smith
Community Expert
Community Expert
May 26, 2026

You should always Start here https://community.adobe.com/community and find the correct forum for your question

kglad
Community Expert
Community Expert
May 26, 2026

or, if looking for the adobe sign developer forum, https://community.adobe.com/acrobat-sign-developer-22

leo.r
Community Expert
Community Expert
May 26, 2026

I assume you need this forum (you may need to change the title slightly to avoid a duplicate post error):

https://community.adobe.com/adobe-acrobat-sign-28