Can't create transient document with group permissions

[jbarr_metro]

Previously, I had created an OAuth token with permissions to read, write, and send agreements for myself and I was able to complete the workflow through creating transient documents, creating and sending an agreement to be signed, checking the agreement status, and signing the agreement and sending completed documents to the signers.

Now I've created an app with permissions to read, write, and send agreements for the group. I am a group admin, so that shouldn't be the issue. I'm able to create a token that's ostensibly compatible with these permissions. But when I submit to /api/rest/v6/transientDocuments using a dummy file and the Bearer token I received I get the following response:

{
    "code": "PERMISSION_DENIED",
    "message": "The API caller does not have the permission to execute this operation"
}

Why am I not able to create a transient document using the token I generated with an account that has the appropriate permissions?

If I add an x-api-user header with email:<my email address> as the value, I get the same error, so it's apparently not that it needs further identifying information.

Is there a permission I need to set besides agreement_read:group, agreement_write:group, and agreement_send:group?

[Meenakshi Negi]

Hello,

Thank you for reaching out and sorry for the delay in response.

I have checked that you are using the Adobe Sign Developer account.

As you have a query related to the API integration, it can be best answered by the experts.

I would request you to contact the pre-sales team. They will be able to provide you the pre-sales technical assistance and share the right information.

Please refer to the following link to get in contact with them: https://acrobat.adobe.com/us/en/sign/pricing/plans.html. You may use the contact button for Adobe Sign business and enterprise under the Multi-User tab.

Let us know if you need any help.

Thanks,

Meenakshi

[SimonESATS]

It's worth checking if you are able to use the method on the swagger page:

post /transientDocuments

agreement_write:group is all that is needed. It's more like to do with your access token user (the owner of the api application), or perhaps the group settings.

Still it's worth just doublechecking the request for the access token has the right scope set as well. (so not in the application itsef, but as part of the Get request.)