Retrieves the consented UserInfo in Twilio Oauth

What this operation does

Retrieves the consented UserInfo and other claims about the logged-in subject (end-user).

• GETReads dataoauth.twilio.com/v1/userinfo

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. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Twilio Oauth operations

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

All 5 Twilio Oauth operations

Questions

Can HumDay retrieves the consented userinfo 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.

Does this change anything in my Twilio Oauth account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Twilio Oauth.

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.