Our documentation actually do mention to use internal name of the property (in the paragraph of description at the top). But I see how it could be clearer if we ensure the consistency of the language i.e. in the Optional parameters table the description does not state internal name. I'll work with the team on this, thank you for the feedback!
Hi @ChipCoons , can you verify that the content-type is being set to application/json correctly? We’d normally only return that 415 error if there was a problem with that content-type header, otherwise you’d get some other 4xx error if there was some other problem with the request.
Thank you for providing the request headers and body. Checking on the ticket property in your portal, the internal name of the property is upload_url. You would need to match exactly the internal name of the property in the request body, including capitalization. Let me know if changing that works for you.
Might I suggest the documentation explictily state that the internal property name must be used?
I used the propery name displayed within the ticket interface for properties and did not pay much attention to the internal name when I created the property. The name I entered had capital "URL" but that is only the lable.
Our documentation actually do mention to use internal name of the property (in the paragraph of description at the top). But I see how it could be clearer if we ensure the consistency of the language i.e. in the Optional parameters table the description does not state internal name. I'll work with the team on this, thank you for the feedback!
Could you pleae proide us internal keys for all the properties for Ticket .I am trying to update Owner, could not find any where the internel key for Owner and couple other properties of ticket.