Bryan Flynn

Hi @...,

Please give the API call that you are making at any returned HTTP status codes (removing any confidential information of course).

Are you using the example cURL code in the reference documentation for POST /api/v2/uploads.json?

Also check out another community post where the tool Postman was used for a file upload: Unable to upload image file via /api/v2/uploads.json through postman

Keep in mind that uploading and attaching to a ticket is a two step process described here: Attaching files to tickets via API.

Hi @.... Looks like this question was also cross-posted in the developer community. I posted an answer there — please see https://develop.zendesk.com/hc/en-us/community/posts/360050023554/comments/360012872554. If you have follow-up questions, I can answer them there. Thanks!

Hi Brandon. It is a bit confusing. There's the ticket field's meta information (the example you gave), which is the "schema" of the field, no matter the ticket. Then there's the custom field's actual value stored for a given ticket.

To get the a custom field's value for the currently displayed ticket use:

client.get('ticket.customField:custom_field_123456789')

Hope this helps!

Hi @... -- I suggest submitting a ticket, so your specific account can be examined more closely. 

Know that this particular workflow is not officially supported. See Can I use a trigger and a target to update tickets? for more details.

Closing this post -- moved conversation over to AMA post: https://develop.zendesk.com/hc/en-us/community/posts/360037266834-Doubts-about-Authenticating-Zendesk-in-your-server-side-app

Hi Calum -- just to clarify, a new request/ticket created by an end user using an OAuth/Bearer token should work.

To simplify the above and using the cURL command line tool, the request would look something like:

curl -v -H "Content-Type: application/json" -H "Authorization: Bearer d482cccebdd482cccebdd482cccebdd482cccebdd482cccebdd482cccebd" https://yourownsubdomain.zendesk.com/api/v2/requests.json -X POST -d '{"request":{"subject":"Test Ticket Subject","comment":{"body":"Test Ticket Body"}}}'

You can quickly generate an OAuth token for the above example using your own account and end-user by:

1. In an incognito browser window, go to https://developer.zendesk.com/requests/new

2. Enter your Zendesk instance's subodomain

3. Click Authorize (then select 'Allow' in the popup window that's displayed if needed)

4. Then copy the entire returned OAuth token

I would not recommend using the "API Token"/Basic authorization approach from a client-side solution -- it exposes your account to possible abuse. By switching out the email address before the "/token" portion, you can impersonate other users. You should only use an API token within the context of a secure server-side solution (one that will not expose the API token to any client agents).

Hi Felipe. GET /api/v2/ticket_fields.json will return all ticket fields in your instance regardless of what Ticket Form they're used on. As for searching, the link you gave is the best reference for what is searchable.

If you're looking for the ability to search a specific custom field, the 'fieldvalue:' option is the closest there is. It searches all custom fields, however -- you can't currently search only a specific custom field. This is a very popular feature request that has yet to be implemented. Hope this helps move you forward.

PS -- Also thanks McCabe as well for the above answer!

Here's the syntax for getting a custom field's value:

client.get('ticket.customField:custom_field_12345678')

...where the '12345678' value is *your* custom field's unique ID, prefixed by the literal string "ticket.customField:custom_field_"

This is documented here:

https://developer.zendesk.com/apps/docs/apps-v2/support_api#ticket.customfieldfieldname

One way of getting your custom field's ID value in Zendesk is by going to to Admin > Manage/Ticket Fields > edit -- it will be listed at the top of the Ticket Field Edit page.