Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • As you may know the service accounts don't belong to an individual end user, but to an application.You can use a service account to access data or perform actions by the account itself, or to access data on behalf of Google Workspace. Refer to this link: Control API access with domain-wide delegation and let me know if it is helpful. Commented Feb 25 at 8:56
  • And most importantly make sure that the Gmail API is enabled in your GCP for the service account to interact with Gmail and to enable google workspace API refer to this official documentation and ensure that service account is impersonating the correct user account. Commented Feb 25 at 9:02
  • Also to access user data on a Google Workspace domain, the service account that you created needs to be granted access by a super administrator for the domain. Commented Feb 25 at 9:04
  • Did you have time to check my comment? It helped you to solve your issue? If not,I am happy to assist further Commented Feb 26 at 4:14
  • @ImranPremnawaz, actually the admin had some routing settings for this particular account, hence it was not saving the history. Once I asked him to keep the history, it started returning via the history list API. So this issue is resolved. The service account already had domain wide delegation etc. Thanks for your help though. Really appreciate it. Commented Mar 8 at 7:38