Via object reference

Hey Josh Lowery, 

The via parameter as a whole isn't required. Though if you're going to use it, then yes you'll be wanting to include both the to/from fields (always as objects).

Thank peeps for such a beautiful conversation. 

Is there a formal definition of the source object? The documentation I've found it's definitive.

Specifically, are the to/from field required and are they always objects?

Hi,

What would be the value for "channel" if a ticket is submitted after logging in to Zendesk? Would the value be different if the agent is using a web/mobile version of Zendesk?

My use case is to track the ticket activities performed by the agent after logging in to Zendesk(and not any other channels like email, API etc.)

Thanks!

Perfect, that worked! Thanks so much

Hi Tommy Newman! In order to get the email address in this case, you would need to pull the requester_ID attribute in Tickets and then you could make a request to the User's API to grab that from the email attribute. 

Hi Bryan - Community Manager

Thank you for your answer. This coincides with my observations.

As a solution I put some recognizable extra text in the ticket's subject so that our agents can recognize that the ticket's coming from external.

Hi. I am trying to get the email address that was used to complete a web_widget form, but it doesn't exist in the via>source>from attribute (as confirmed in the table above). The email address does existing on the ticket within ZenDesk, but I cannot see how to get it through the API. Can anyone shed some light on this please?

Hi Andy Loeber,

Setting "via" is very limited — in this case, because it sounds like you're going through POST /api/v2/tickets, the system sets it and you don't have control.

It's more of an indicator of the entry point into Zendesk (in this case the API), rather than what external system the data might be coming from.

Even for APIs that can set it (example: POST /api/v2/channels/voice/tickets.json) the options are limited.