Fetch a specific Participant in Twilio Proxy
A documented Twilio Proxy operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Fetch a specific Participant.
- GETReads data
proxy.twilio.com/v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants/{Sid}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Twilio Proxy operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Twilio Proxy operations
- Create a new Service for Twilio ProxyPOST · changes data
- Create a new SessionPOST · changes data
- Create a new message InteractionPOST · changes data
- Add a Short Code to the Proxy Number Pool for the ServicePOST · changes data
- Add a Phone Number to a Service's Proxy Number PoolPOST · changes data
- Add a new Participant to the SessionPOST · changes data
- Delete a specific ServiceDELETE · changes data
- Update a specific ServicePOST · changes data
Questions
- Can HumDay fetch a specific participant in Twilio Proxy?
- Yes. This operation is published in Twilio Proxy'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 Proxy 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 Proxy.
- 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 Proxy account.
Where this came from
Read from a published API description for Twilio Proxy at raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_proxy_v1.json. The description above is the provider’s own wording, not ours. Last published 2023-04-20.