Андрей Семенцов

Hello, Sara.

Which ticket platform you wish to migrate to?

For your request try to use this endpoint it's more relevant for Ticket events, but i see, it contain and other information you needed:

https://{account}.zendesk.com/api/v2/tickets/{ticket_id}/audits/

Lina Akkad
I think it's possible to make via trigger.

Conditions.
Ticket Is Created
Form Is Your_form

Actions.
Email user  (requester)
Message:
--------- --------- ---------
Hello, sweetie!
We received your request with following information.
Field1: {{ticket.ticket_field_111111111}}
Field2: {{ticket.ticket_field_22222222}}
Field3: {{ticket.ticket_field_333333333}}
We'll answer you asap.
--------- --------- ---------

Have same issue.
Want to get #{{ticket.id}} as a plain-text (not as url), and have no solution.

I checked, indeed, I have sent an incorrect api request, the format was different from the api description.
I checked new View creation, and param "sla_next_breach_at" of the "output" "columns" branch is processed correctly. It was my mistake.
Thank you for your support.

Have a good day!

I already pay for Zendesk.
And I need to do something else so that you can fix your mistakes with incomplete api for my money?
You already know about problem. You can feel free to do what you want with my report yourself, I don't mind. 
I want to get normally functionality product, which have completed API.
For now the API does not cover all functionality of the web interface.

I have made this request on the recommendation of your Zendesk support. Although I sure that request must have been issued by the Zendesk support, and not by me personally.

My request: https://support.zendesk.com/hc/en-us/requests/10564542

I hope that you will make every possible effort to solve this problem.

Good luck!

Good day! 
I faces with problem that the Zendesk API has a weak functionality that does not cover the capabilities of the web interface. The problem is observed with the Views in Business Rules section.
Our company uses Views that include the "Next SLA breach" column.
When I executing an API-request to display the View options(columns), which was created through the web interface, I get information about the presence of the following id in the column branch:
{ "id": "sla_next_breach_at", "title": "Next SLA breach" }

But when I want to create a new View via API in which I need to use the "Next SLA breach" column, then adding to the api request, in the columns branch:
{ "id": "sla_next_breach_at", "title": "Next SLA breach" }
this id is ignored and I get a View without the column that I needed.

Yes, I can add it via the web interface. But I use the API specifically, because I don't want to do nothing via web-interface.

And fixing something that is not covered by the API, for example, when you need to create 100 Views, is catastrophically inconvenient.

Zendesk support confirmed that this column cannot be added with Create request via Zendesk API.

Otherwise, the ideology of your API, as such, loses its logical meaning.

I ask you to bring the API into a state that will cover all the functionality of the web interface.

Thank you!