Adding Attachments to Tickets
|
|
Does anyone have any example code where they have added used the Unfuddle API to add attachments to tickets? thanks, |
|
|
It seems that the unfuddle api doesn’t provide the attachment information. If you export all tickets information into an csv document, there wouldn’t be attachment information such as attachment id. |
|
|
Lilin, The Unfuddle API does indeed support Attachments for ticket, messages, notebooks and comments. You can find more information in the API documentation Of particular note, uploading and saving attachments is a two-step process unlike most other API interactions. |
|
|
David C., The API docs are a nice ref for field names but exactly how the flow is and how to upload a f.i. a PDF to Unfuddle is not clear to me. Should we encode the file contents with base64? Or do we provide an remote url? or else…? |
|
|
As the documentation states, the attachment upload process actually consists of two steps. In short, it looks something like the following (using curl as our client): REQUEST 1:
RESPONSE:
REQUEST 2:
As explained in the documentation, you must first upload the file. Once this has completed, the server will respond with an upload key which must be used in the second request. This second request tells Unfuddle to actually create the attachment object and associate the file data you previously uploaded with that object. All this being said, you must be using an account plan which supports file attachments (i.e. not the Private plan). If you are still unable to get this to work, please send us a transcript of your attempt(s) and we will be happy to assist you further. |
