Copy link to clipboard
Copied
We have a custom proprietary tool that uses the Adobe Sign engine for sending docs. Our integration allows for users to send using a service account, which means not all of our internal users need to have an Adobe account. This morning, on a newly created doc template, a user attempted to send the doc and is receiving an Adobe error I haven't seen before: INVALID_GROUP_ID_FOR_USER. Not sure where in the process this is occurring, since the user doesn't technically have an Adobe account, it's using our service account as it does for all doc sends.
Hello! We experienced the same error when calling the POST /api/rest/v6/agreements endpoint to create a new Agreement, after adding a groupId parameter to the request it started returning:
[{"code":"INVALID_GROUP_ID_FOR_USER","message":"Specified group is invalid or user is not a member."}]"}
If we removed the groupId parameter everything instantly worked again so clearly something was up with adding that to the request, but everywhere we looked the user making the request had the correct grants/a
...Copy link to clipboard
Copied
Hi dstinsman,
Thank you for reaching out.
We have checked that you are using the Adobe Sign Enterprise plan. This is something that the experts can best answer. Please contact our Adobe Sign Enterprise support team for the correct information. You may contact them using the steps in the following help document: https://helpx.adobe.com/sign/using/adobesign-support-resources.html.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Hello! We experienced the same error when calling the POST /api/rest/v6/agreements endpoint to create a new Agreement, after adding a groupId parameter to the request it started returning:
[{"code":"INVALID_GROUP_ID_FOR_USER","message":"Specified group is invalid or user is not a member."}]"}
If we removed the groupId parameter everything instantly worked again so clearly something was up with adding that to the request, but everywhere we looked the user making the request had the correct grants/access.
After a lot of checking different parameters, user permissions, emails and everything else we finally figured out that the Bearer Token for the user that was used in the request (which was different from the api-user, on-behalf-of-user, agreement manager, etc.) did not have permissions to the groupId.
After adding that user to the group and giving Admin access it started working...
Copy link to clipboard
Copied
Thank you for reaching out and sharing the information.
Glad to know the issue is resolved. The information you share may help others in the community with similar problems.
We have checked that you have the Adobe Sign Enterprise plan. If you need any help with integration, we suggest you contact our Adobe Sign Enterprise support team for the correct information. You may contact them using the steps in the following help document: https://adobe.ly/4hn5eR1.
For more information on Acrobat Sign integration, please refer to the following help document: https://adobe.ly/41VESRF.
Thanks,
Meenakshi
Find more inspiration, events, and resources on the new Adobe Community
Explore Now