Issues a new Access token (optionally identitytoken & refreshtoken) in Twilio Oauth

What this operation does

Issues a new Access token (optionally identitytoken & refreshtoken) in exchange of Oauth grant

• POSTChanges dataoauth.twilio.com/v1/token

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 Twilio Oauth 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 Twilio Oauth operations

• Issues a new Access token (optionally identitytoken & refreshtoken)POST · changes data
• Retrieves the consented UserInfoGET · reads data
• Fetches public JWKsGET · reads data
• Fetch configuration details about the OpenID Connect AuthorizationGET · reads data

All 5 Twilio Oauth operations

Questions

Can HumDay issues a new access token (optionally identitytoken & refreshtoken) in Twilio Oauth?

Yes. This operation is published in Twilio Oauth'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 Twilio Oauth data?

Yes — this is a POST operation, so it changes something in Twilio Oauth. 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 Twilio Oauth account.

Where this came from

Read from a published API description for Twilio Oauth at raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_oauth_v1.json. The description above is the provider’s own wording, not ours. Last published 2023-04-20.