Article Attachment API throws 500 error | Community
Skip to main content

Article Attachment API throws 500 error

  • October 30, 2025
  • 2 replies
  • 0 views
Stefan19

i'm running this request (curl version, but the same is happening in a java application)

 

I'm following this guide: 

https://developer.zendesk.com/api-reference/help_center/help-center-api/article_attachments/#create-article-attachment

curl https://{domain}.zendesk.com/api/v2/help_center/articles/35853340916247/attachments.json \                                                                                                                                    
  -F "inline=false" -F "guide_media_id=01K8TCJMYFDE3EY9VPQKWE00E1" \
  -v -u {email/token} -X POST

the article id and guide_media_id are actual ids, i redacted my auth string and my domain name. If this is a specific issue, i hope you can contact me, otherwise please advise how i can get support.

    2 replies

    Greg29
    • Greg29
    • October 30, 2025

    Hi Stefan! 

    I was able to find this 500 in our logs and from what I can see, everything looks correct. While it doesn't make sense to return a 500 if this were the case, could you confirm that the guide_media_id is correct? You need to be sure that it hasn't been deleted/belongs to the account that you're uploading it from. If it is the right media_id and it's from your subdomain, drop me a line here and I'll open up a private ticket to investigate this further for you.

    Stefan19
    • Stefan19
    • Author
    • October 31, 2025

    Hello Greg!

     

    Thank you for investigating! I was able to resolve the issue. I missed stepped 3, creating a guide media object because i mistook the `asset_upload_id` for the `guide_media_id`. I should read the documentation more clearly :). Hopefully this helps others who have a similar issue to resolve it faster.

     

    Ideally this would have produced a 400 error and a message that the `guide_media_id` could not be found. This would have helped me resolved the issue faster. Thanks again for your help!

    Terms & ConditionsCookie settingsAccessibility statement