Generates an OAuth 2.0 access token for a service account in Google IAM Account Credentials

What this operation does

Generates an OAuth 2.0 access token for a service account.

• POSTChanges data · projectsiamcredentials.googleapis.com/v1/{name}:generateAccessToken

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Google IAM Account Credentials operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google IAM Account Credentials operations

• Signs a JWT using a service account's system-managed private keyPOST · changes data
• Signs a blob using a service account's system-managed private keyPOST · changes data
• Generates an OpenID Connect ID token for a service accountPOST · changes data

All 4 Google IAM Account Credentials operations

Questions

Can HumDay generates an oauth 2.0 access token for a service account in Google IAM Account Credentials?

Yes. This operation is published in Google IAM Account Credentials's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Google IAM Account Credentials data?

Yes — this is a POST operation, so it changes something in Google IAM Account Credentials. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google IAM Account Credentials account.

Where this came from

Read from a published API description for Google IAM Account Credentials at iamcredentials.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.