![]() provided as criteria to match any resource that contains the string in its value. Priority wise I believe the queries by ID and updated date are the most important because those would at least make it possible to check for recent updates or new entries after some starting point, which is crucial functionality for many integrations. You can query the REST API by entity ID or by using filter expressions. The result of this query will give me the first 1.000 tickets created. Primary candidates for filter conditions would be: This function is very useful and has a lot of parameters that can be used to call. It would be very helpful to be able to query by certain conditions or in other words filter. This is of very limited usefulness given that an instance may easily contain thousands upon thousands of time entries. This would mean the URI was not 'human readable', but I would argue that URI encoded JSON isn't particularly easy to read either. ![]() For example, the following URL has two query params, sort and page. If you did still want to use the query string, another option would be to base64 the JSON string, meaning you wouldnt need to worry about escaping the spaces and special characters. ![]() At least, that is all that is documented ( ). Query parameters are optional key-value pairs that appear to the right of the in a URL. Currently it appears that the only way to retrieve time entries with the REST API is to either list all time entries or request them one at a time by ID. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |