Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Dylan McKinney
Beigetreten 12. Okt. 2022
·
Letzte Aktivität 22. Mai 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
11
Stimmen
3
Abonnements
4
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Dylan McKinney
Dylan McKinney hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 22. Mai 2024 · Dylan McKinney
0
Follower
0
Stimmen
0
Kommentare
Dylan McKinney hat einen Post erstellt
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:
Gepostet 29. Nov. 2023 · Dylan McKinney
0
Follower
1
Stimme
0
Kommentare
Dylan McKinney hat einen Kommentar hinterlassen
Thanks for the quick response! It looks correct now.
Kommentar anzeigen · Gepostet 12. Okt. 2022 · Dylan McKinney
0
Follower
0
Stimmen
0
Kommentare
Dylan McKinney hat einen Post erstellt
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
Gepostet 12. Okt. 2022 · Dylan McKinney
0
Follower
2
Stimmen
3
Kommentare