Pesquisas recentes
Sem pesquisas recentes

Dylan McKinney
Entrou em 12 de out. de 2022
·
Última atividade em 22 de mai. de 2024
Seguindo
0
Seguidores
0
Atividade total
11
Votos
3
Assinaturas
4
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Dylan McKinney
Dylan McKinney comentou,
Thanks to John Mahoney for your response. I am using classic ASP.NET and didn't realize I needed a solution that worked from the client side. For me the solution was returning a page similar to this where it auto submits the form and triggers the redirect.
The Zendesk-provided github sample would be applicable if the user was submitting a form where the script is written client-side.
Exibir comentário · Publicado 22 de mai. de 2024 · Dylan McKinney
0
Seguidores
0
Votos
0
Comentários
Dylan McKinney criou uma publicação,
I am experiencing a new issue when creating a help center article attachment. When attempting to create the attachment, I receive a 400 status code and the following error:
{
"errors": "content_type Expected asset of type application/xml but got audio/mpeg"
}
The endpoint I am using is documented here:
I have an application calling the following endpoint:
POST /api/v2/help_center/articles/{article_id}/attachments
The file in question has a proprietary file extension used by my organization, so common methods of deducing the file type may be unreliable. When sending a similar request in Postman, I must use multipart/form-data for the Content-Type header or I receive a 400 response with the following error:
Publicado 29 de nov. de 2023 · Dylan McKinney
0
Seguidores
1
Votos
0
Comentários
Dylan McKinney comentou,
Thanks for the quick response! It looks correct now.
Exibir comentário · Publicado 12 de out. de 2022 · Dylan McKinney
0
Seguidores
0
Votos
0
Comentários
Dylan McKinney criou uma publicação,
The documentation for the Bulk Delete Sessions endpoint lists the HTTP method as GET when it should be DELETE:
GET /api/v2/users/{user_id}/sessions
As done in the Using curl portion of the documentation, the -X DELETE argument indicates the DELETE HTTP method is to be used:
curl https://{subdomain}.zendesk.com/api/v2/users/{user_id}/sessions.json \
-v -u {email_address}:{password} -X DELETE
Publicado 12 de out. de 2022 · Dylan McKinney
0
Seguidores
2
Votos
3
Comentários