Búsquedas recientes
No hay búsquedas recientes

Emily Prachnau
Incorporación 16 oct 2021
·
Última actividad 16 oct 2021
Seguimientos
0
Seguidores
0
Actividad total
5
Votos
0
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Emily Prachnau
Emily Prachnau creó una publicación,
Feature Request Summary:
Zendesk Sell deals firehose API endpoint should have every field that the Core API deals endpoint has. Right now, the firehose API doesn't not have every field that the core API has. For example, the firehose API is missing the unqualified_reason_id for deals.
Description/Use Cases:
An application continuously consumes from the deals firehose API endpoint (/v3/deals/stream) and actions are triggered on certain changes. One of these actions requires the unqualified reason. Since the unqualified_reason_id is missing, the app has to do an additional lookup at the deals endpoint (v2/deals) to get the unqualified_reason_id field.
With this workaround, the application doesn't know what the unqualified_reason was before it was changed.
Business impact of limitation or missing feature:
We aren't able to track the unqualified_reasons using the deals firehose API, which is valuable for gathering data and monitoring why deals were unqualified.
Publicado 20 ago 2021 · Emily Prachnau
1
Seguidor
1
Voto
0
Comentarios
Emily Prachnau hizo un comentario,
Thanks Kaja, I'll post it there.
Ver comentario · Publicado 20 ago 2021 · Emily Prachnau
0
Seguidores
0
Votos
0
Comentarios
Emily Prachnau creó una publicación,
I have an application that consumes from the firehose API /v3/deals/stream endpoint and the unqualified_reason_id field is not present.
If I query /v2/deals, then the unqualified_reason_id field is present.
Are there plans to add unqualified_reason_id to the firehose API for deals so that it matches v2 endpoint?
Publicado 18 ago 2021 · Emily Prachnau
0
Seguidores
2
Votos
2
Comentarios