Developer app OAuth works, but agreement scopes are unavailable: plan requirement?

Question

I have an Adobe Acrobat Sign developer account and registered an OAuth application for a test manuscript-submission workflow. The OAuth authorization flow completes successfully and returns a token with the user_read:self scope.

In the app’s OAuth scope settings, agreement_write:self and agreement_read:self are unavailable or disabled. The page indicates that support must be contacted to change the available scopes. Adobe’s virtual assistant also says it can’t associate an active Acrobat Sign plan with my account.

Is this expected for a developer account? Can these agreement scopes be enabled for a developer or test application without purchasing a paid Acrobat Sign subscription? If a paid plan is required, which lowest-cost plan supports these scopes and API testing?

I’m looking for the right technical guidance or support channel. I have not included credentials, application IDs, or secrets.

Ten A · Answer

When I run through the demo code below, the authentication is successful, so it seems that there is no problem with the agreement scope.

https://secure.jp1.adobesign.com/public/oauth/v2?
redirect_uri=https%3A%2F%2Fsecure.jp1.adobesign.com%2Fpublic%2FoauthDemo&
response_type=code&client_id=9MEJXY4Y4R7L2T&scope=agreement_write&state=QW0GDNV4NPEM94X35ASN

But if I add the `account` scope alongside `agreement_write`, access is denied for the `account` scope.

Regarding Acrobat Sign, AFAIK, the annual subscription cost is in the range of $300–$400/year, but you would need to obtain a formal quote from a reseller.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.